I currently have a single back end access200 database, with two front ends.
Built into the two front ends is a link to a further backend with a single yes/no table, which interrogates this file every so often, if its set to yes, then it forces that front end to quit, and doesn't allow access to either front end anymore...
Usually what happens is the back end crashes, i kick everyone off, repair it, and off we go again, all hunky dory..
Unusually, whats happened today, is that one of the front ends, has crashed. I've kicked everyone off, but file locking is present on both the front end that i suspect has crashed, and the back end main db. (which i have confirmed is ok but going through the other front end)
So my question.. (and i suspect there is not a lot i can do), is how to get rid of the record locking, and gain exclusive access to it all again.
One of the things that i have considered, but discounted it, because this happens so rarely, and would involve a fair bit of work, is to register everyone's log in, when they log in, ie: their Windows network log in, to a file in the second back end. then log them out from this, as they leave the db. This would of course when it crashed, allow me to pinpoint the guilty person/ machine.
PS: can anyone recommend a database that has all the usability of Access, but none of its horrible limitations and bugs ?