jdebill
Active Member
Asynchronous Option Doesn\'t Work On Server Based UBE
Hi All,
This is a follow-up post my earlier one about the UBE not returning a value.
I am very curious why the tool set will allow you to specify that you expect the calling object to wait until a called UBE finishes processing (non-asynchronous call), and NOT wait!
When reading the JDE Developers Guide's CNC section it seems to indicate that a calling application will have the results of the call returned from the called object.
Can someone tell me if I'm missing something here? Shouldn't you be able to get the results, thru the interconnect data structure on a non-asynchronous call when an object executes on the server instead of locally?
If not, then you can never code expecting to wait for the returned information as you don't know how the CNC mapping may change in the future. I thought the whole purpose of CNC was to separate the logic requirements from the configuration.
Thank You,
Bill
Windows NT, SQL 7, XE 17.0
Hi All,
This is a follow-up post my earlier one about the UBE not returning a value.
I am very curious why the tool set will allow you to specify that you expect the calling object to wait until a called UBE finishes processing (non-asynchronous call), and NOT wait!
When reading the JDE Developers Guide's CNC section it seems to indicate that a calling application will have the results of the call returned from the called object.
Can someone tell me if I'm missing something here? Shouldn't you be able to get the results, thru the interconnect data structure on a non-asynchronous call when an object executes on the server instead of locally?
If not, then you can never code expecting to wait for the returned information as you don't know how the CNC mapping may change in the future. I thought the whole purpose of CNC was to separate the logic requirements from the configuration.
Thank You,
Bill
Windows NT, SQL 7, XE 17.0
