Hi All,

Lately I've been getting my feet wet with MS-SQL7 by re-writing a "Guinea Pig" application to use either SQL or Fox tables (with minimal code changes). The app contains a form to enter transactions, along with another form to run the posting process. With VFP tables, it was easy - the posting routine tries to use the transaction batch exclusive and either gets it or not. Other users were kept out of transaction entry during the posting process. I'd like to duplicate this functionality using SQL7, but I'm running into problems.

My first attempt was to "Table Lock" the transaction batch during the posting process. If the posting process is started first and a user tries to enter a transaction, they're prevented property. If the user starts entering a transaction (does not complete) and a different user starts the posting process, they can get the "table lock" properly, even though there's an outstanding transaction against the table. I wouldn't think that SQL would allow that (remember - I'm just starting to think in SQL). Is there a technique for getting around this issue or am I trying to impose "dbf think" onto an SQL problem?

Thanks in Advance!