Also, only the record being edited is locked and inaccessible to other users for editing, so unless you know that the same user is logging onto multiple PCs at the same time, you're unlikely to see any problems with this.
If your organisation is such that potentially hundreds of users will all log on at exactly the same time, thus preventing further connections to the .mdb file, then you could potentially have multiple .mdb's, which the script lets the PC write to based on site or OU membership, and a central .mdb which runs an append query to pull all the disparate tables together.
Possibly it would be even more manageable this way for a web based app, as you could decide which segment of the db to query without having to trawl through all the available records. In theory, only the inventory script is going to write to this db, whether it runs at logon or not.
[Edit] Or perhaps I've misunderstood your concerns? Potentially, I've overused the word "potentially", as well.... [/Edit]
[ 04. November 2003, 09:09: Message edited by: Breaker ]
_________________________
================================================
Breaker
