Larry's analysis is exactly correct. The question became
one of how to get the system, in this case Windows Server
2000, to release the locks on the database files. At that
point it is no longer an issue which can be solved within
R:Base. You must use server management tools to release
the locks. After a while the locks simply go away but
that is usually after at least a day or two.
Bernie
At 01:56 PM 1/16/2007, you wrote:
<<Now the question is when does it not work?
>>
My guess is "when the operating system reports another lock on the file". I believe what's happening is that when you start R:Base it checks the file to see if it can get an exclusive write lock. If it can, it locks the file, opens it, performs "maintenance", closes it, then reopens it in shared write mode. If the operating system "believes" a lock exists on the file the exclusive write will fail and R:Base will act as if it's in multi-user mode (which it really is).
Using SET MULTI OFF before you connect will alert you to situations in which you _think_ you're the only user in the database, but the operating system says otherwise.
--
Larry
