Lewis Mccabe

Rob, I just typed a very in dept discussion for you but was not logged in. Text was not retained. I will be a bit shorter but here is the gist: We have been printing barcodes from PROIV for 30 years. Presently, and for the last 10 years, we print warehouse labels using Zebra printers. Other manufactures are fine too but this is what we have settled on. FedEx uses Zebra and that is good enough for us. Zebra has a label design program which is free called "Zebra Designer". You can do anything with it - all symbologies, QR codes, many fonts, graphics, etc. In the label design, we put our PROIV variables which will be replaced at print time. We print to the Zebra printer using a generic text driver. Works like a champ. Labels look excellent and the time from print to when you have a label in your hand is about 2 seconds for a 4"x6" label. Faster for smaller labels. Our customers print millions of labels per year using this method. I can't remember the last time we had an issue with it. On the scan side, there is nothing really related to the software. Plug and scan. Give us more information on what configuration you are looking to implement. Lew

Hi Neil,

Haven't spoken to you in a while. I hope all is well. Thanks for the info. I especially like that version 8 came up clean. .2 release was because we found an issue in linkage when importing older source from a large vpx file. I have to say, Northgate fixed it promptly.

Speak to you soon. Lew

Thanks Neil.

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.

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.