Thank you for the response. To assist in narrowing down any variables as narrow as possible, is there any issue with reverting back to the previous compiler exe? If I still see the symptoms with the previous verison, then it would be proven not to be the new update but some other factor that has crept in.
However, I was hesitant to move back to the previous version once the database has been active with the latest update, not knowing if any behind the scene functions would make it unwise to revert back. Again, thank you for your assistance. Bob ----- Original Message ----- From: "A. Razzak Memon" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Monday, March 2, 2015 3:11:26 PM Subject: [RBASE-L] - Re: Data insert issue after installing latestupdate At 03:47 PM 3/2/2015, [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. Bob, I have always admired your posts and your positive attitude on this list. The way you have explained your situation, and the behavior of the application after the update, is something that we take very seriously. And, yes, while we are optimizing, we have also been tightening the code. I will personally experiment this with my own application samples and see if I can find any oddities. Meanwhile, if you can prepare a quick sample to replicate, please send everything to [email protected]. Very Best R:egards, Razzak. www.rbase.com www.facebook.com/rbase -- 32 years of continuous innovation! 17 Years of R:BASE Technologies, Inc. making R:BASE what it is today! --
