Ron Baum wrote:
To clarify my use of the locking.
We have an ordering system that all the sales people have access to. I am trying to prevent Sales Person #1 from opening an order looking at it...Sales Person #2 opening the same order and making a change...Sales Person #1 saves his/her changes and overwrites Sales Person #2's changes.
In addition this system uses legacy data which is in FoxPro free tables (this is not my choice).
Hope this clarifies my question.
Yew, this clarifies your question. If you can't handle the lock at database level as in FoxPro tables, the solution that i figure out could be a shared object between all the users. Something like a thread semaphore in thread programming. I'll do some investigation on that hope this helps azazel