Graham Brown (CompSYS) wrote: > btw the scenario I have is exactly as you say, a parameters table holding > the next available number. I had a bit of a problem a couple of years ago with the same scenario but we had two systems accessing the parameter table. The first was our old FPD 2.6 system and the other our newer VFP7 system. It appeared that VFP was cacheing the table and could not tell that the old system had updated it, even though we were using RLOCK() then unlock etc. What I had to do to make it work was get VFP to close the table after it had got the number. It gave me a right headache with duplicate barcode numbers. :-(
Peter _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
