stopping .idb file creation

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Problem: When a user opens my Frontend.mdb, but is not joined to the
workgroup, the splashscreen opens, and the database hangs. An .idb file is
created for both the Frontend.mdb and the linked Backend.mdb. The user is
forced to use CTRL-ALT-DEL and End Program, which leaves the .idb files
intact - meaning I can no longer open either one exclusively to edit them.

Setup: Office XP. ACCESS 2002. Multiuser environment. Security workgroup for
both frontend and backend.

Question: How do I programmatically block users who are not joined to the
workgroup from getting far enough into the database opening sequence to cause
the creation of the record-locking file? Or how do I identify that the user
attempting to open the database is not joined to the workgroup (in the code
of the startup form or module) so that I can force them back out gracefully?

Thanks
 
dkhtx said:
Problem: When a user opens my Frontend.mdb, but is not joined to the
workgroup, the splashscreen opens, and the database hangs. An .idb file is
created for both the Frontend.mdb and the linked Backend.mdb. The user is
forced to use CTRL-ALT-DEL and End Program, which leaves the .idb files
intact - meaning I can no longer open either one exclusively to edit them.

Setup: Office XP. ACCESS 2002. Multiuser environment. Security workgroup for
both frontend and backend.

Question: How do I programmatically block users who are not joined to the
workgroup from getting far enough into the database opening sequence to cause
the creation of the record-locking file? Or how do I identify that the user
attempting to open the database is not joined to the workgroup (in the code
of the startup form or module) so that I can force them back out gracefully?
Click to expand...

I can't explain the locking, but can tell you that this almost certainly means
that you didn't setup security properly and that is what you need to correct.

When a user attempts to open a secured file with any workgroup besides the one
used to secure it they should simply get an immediate error indicating that they
do not have permission to open the file and that should be the end of it. The
fact that LDB files are being created suggests that they are being allowed to
open the file which is incorrect.
 
Back
Top