I'm assuming your working with an mdb file for the web (if not disregard this).
I wonder if you're able to run a *.vbs script to launch the MSAccess mdb for the web-site (you may have to add the website to the trusted sites for each user to allow running vbs scripts.) If so, you could use something like the cloning script in the code bank. This would at least prevent the *.ldb from locking other users out of the mdb (since every user is in essentially their own mdb cloned from a source mdb.) I'm not sure though without more info on what you mean by web-based database (is this an ASP project?) Or are they just opening an mdb file via the web?
If the website automatically launches the mdb when the user connects, have it instead run the *.vbs script.
If the user opens the website, navigates to a folder, and then opens the mdb, have them open the *.vbs script in the folder instead of the mdb.
All users open my mdb files via vbs scripts so if a user who is connected via the web clicks the X (ie. to close their web citrix session), that mdb file isn't then locked for other users since there will only be a "hanging" *.ldb file for ONLY that specific user (which will fix itself the next time that specific user connects and runs the script again.) (there's also numerous other benefits using the script such as: eliminating the "locked by another user" error for good, unlimited users using the app, knowing who's using the mdb, seeing when they last opened the mdb, copying new code without having users close out, etc, etc...)
I'm guessing that there is a login of some sort through the website. If so, the script should be able to grab the login name (or you can change it to grab the computername). If there's no login, you won't be able to use the script.
Last edited by pkstormy; 08-22-09 at 03:05.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)