on 06-05-2014 11:26 AM
Hello, all
We have successfully ported a PB Classic app to PB.NET and it works without any issues.
The correctly functioning PB.NET app uses a PB.NET assembly (.NET assembly called mailing.dll), which, also has datastores.
Here is the strangest inconsistency.
If the mailing.dll if loaded from the application directly, then it works correctly.
But if it loaded by another assembly, i.e., the loading is Application->Assembly1->Assembly2, then the settransobject function returns errors for exactly the same data without any apparent reason.
Each assebmly has a separate namespace, so the variables could not possibly be interfering with each other.
Has anyone encountered with this problem before? Any direction wouldbe greately appreceated, since I got zero leads right now.
Thank you
Arcady
Hi Arcady;
FYI: I can still reproduce this and other issues in PB.Net that run fine in PB Classic. Maybe SAP will address these in v15.
Regards ... Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, this looks exactly like my case:
http://scn.sap.com/thread/3391198
Only I am not sure I have a possibility of such a workaround.
Does anyone know if there is a solution for this problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.