7 replies to this topic

[Lewis Mccabe]

Hello All,

 

We have a function we want to call within a Windows PROIV MFC session. We want to kick off the update behind the scenes while the customer continues their data entry. We were told this cannot be done in Windows. I see that Developer (VIP) seems to do it. Anyone have an answer? Thanks

Lew

[Wim Soutendijk]

Never used that feature, but you can try to enable it by setting the batchq id in the spooler tab of the update function

[DARREN]

Another option would be to have your U.I. write to a table/file and have a seperate watch process monitor the same and invoke a Gateway/Webservice.

[Lewis Mccabe]

Batch ID can only be used for non global functions. We tried. I know PROIV Developer saves logics behind the scene. Anyone know how they do it?

[Chris Mackenzie]

Batch ID can only be used for non global functions. We tried. I know PROIV Developer saves logics behind the scene. Anyone know how they do it?

 

why is that a problem?   you wrap the required globals in a non-global Update and set that to run in batch.

 

BTW - what reason were you given for batch queue not working in Windows?

 

Someone suggested

[Lewis Mccabe]

The reason we want to have a global update run in batch is because the user is in the middle of the order header function when we want to run this global function (an item price update). The user still has some data entry to complete when we have enough information to fire off the update. It will take them another 5 seconds or so to complete the header screen - about enough time to complete the global update. We would like the item price update to run during this time so to the user, it appears the items are all priced by the time they move from the header to the detail. Currently we have to wait until they finish the header screen (global) and then fire off the global item price update prior to presenting the items in the order detail function. It does not seem like much but when a user is entering 400 orders, it slows him/her down considerably - to the tune of a half hour, or more, of waiting.

 

Batch works fine in windows when a non global function is called. In UNIX we would simply call PROIV from the command level and problem solved. We are told this cannot be done in Windows.

[Chris Mackenzie]

? why not refactor -   set @LFUNCT FNEXIT and then re-enter to where you were in your main function after calling your update..

Edited by Chris Mackenzie, 16 July 2014 - 01:01 PM.

[Lewis Mccabe]

Refactoring is not an option. Highly optimized functions which are complex. We also don't like the UI under those circumstances. As we were developing them, we never in a million years thought we would not be able to kick off a PROIV session in Windows the way we always had in UNIX. Thanks though.