Bob, I have found over the years with updates that sometime it has been 'tightened'. I have used code that had a 'closewindow' within an 'if' loop, and worked fine, but with the upgrade(not last but one before that) I had to get the 'closewindow' outside the 'if' statement and it works fine.
Tom Hart On Monday, March 2, 2015 2:47 PM, "[email protected]" <[email protected]> wrote: Over the weekend, I installed the latest update - Build: 9.5.5.20226 and recompiled my multi-user application. One application that is used constantly, generates barcode labels for produced product. These labels must be scanned by fork lift operators before they can move the product. After the update, we are experiencing an issue where a barcode is generated by production machine "X" and the label printed. The fork lift operator attempts to scan the barcode and the application does not find the new barcode number. The database generated the label, so the number must exist and it does indeed show up on machine "X" computer listing of produced barcodes. If the lift driver exits their program and re-enters, scans the label, the number is now available. This is a long standing program with no changes made. However, I know that new releases can sometimes "tighten up" on incorrect coding and code that ran in the past may see an issue with the new release. I have looked in-depth today and cannot find any obvious coding errors. (I guess if they were too obvious, I would have detected them much earlier!) I am not sure what would cause records not to become available to other sessions until a disconnect / connect was issued. This is not a temp table or structure issue as the program has been in operation for a long time. It must be some code that I have that was marginal and the new release does not like it. However, I am at a bit of a loss to find it. These records are inserted via an EEP inside a form. I do not follow the insert with a Property Table POST command, but did not understand that was required. Is it? The other sessions call the data with a Select .... into ... command. Thanks, Bob
