Re: Help - Security Issue

When you open the mde, you haven't yet necessarily opened the backend mdb.
Once you open a bound form, you'll see the ldb show up for the backend.

Have you tested that the network people set things up correctly?


--
Joan Wild
Microsoft Access MVP

JanetF wrote:
Hi Joan,

Yes, I had network people set up the permissions on the folder. As
to an ldb file, there isn't one in the folder and the mdw file is
named differently from the mdb. I did notice, though, that when I
open the database an ldb file only shows up for the mdw file out on
the folder and for the mde file (front end) on my C drive (where it
is stored). Shouldn't there be one for the back end (data) as well?

thanks,
Janet

"Joan Wild" wrote:

'Had it setup' implies that you had someone else do this. You need
to verify that *all* users have this permission.

You can verify, by having a user open Windows Explorer, and attempt
to create a file in that folder (just right-click, New, text file
will do). If they can create it, can they save it? Can they then
delete it?

If this checks out, it's possible that things weren't cleaned up
from the previous problem.

With everyone out of the mdb, check in the folder to see if there is
any file with a ldb extension. If this file(s) exists, delete
it(them).

Also ensure that your mdw file does not have the same name as the
mdb in the same folder. They each need to create an associated ldb
file; with the same name they can't.


--
Joan Wild
Microsoft Access MVP

JanetF wrote:
I've put this question in here before, but have not resolved my
problem. I have a split database, with the back end out on a
server. The front end is on all user's individual PC's. I also
have a security mdw which I've created and seems to work fine. The
problem I'm having is if more than one person tries to open the
database, they receive an error message saying "Cannot access the
FILENAME, file already in use." What do I do? I was told that
users should have full permissions to the shared folder which holds
the back end. I have now had that set up, but the problem has not
been resolved. Any ideas?

thank you,
Janet


.

Relevant Pages

  • Re: Suddenly CANT DELETE / EDIT Records ???
    ... In the Windows Explorer, open the folder containing your ... See if there is an LDB file there with the same name. ... The LDB contains locking information for the MDB. ...
    (microsoft.public.access.formscoding)
  • Re: All users must be admins?
    ... As far as my experiance is concerned, an LDB is created eveytime an MDB is ... That folder can be placed ... it is not usual to grant admin permissions to users. ...
    (microsoft.public.access.security)
  • Re: Unable to compact/repair because I have it opened
    ... If the mdb file and mdw file have the same base name (like products.mdb and ... they share the same locking db (ldb) file. ... error message saying the file is exclusively in use by on ... the same folder as the BE. ...
    (microsoft.public.access.security)
  • Re: Running an Access macro from a VB.NETprogram
    ... An ldb file is an Access locking file (located in the same folder as your ... If your Access mdb is ... I'm not sure if an ldb would be created against the original file if you use ... My program opens Access to try to do this.. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Networking unsecure database
    ... >> delete the LDB file if they're the last user to leave the database. ... > (with Full Control permissions) can delete it before compacting. ... > protect against accidental or malicious deletion of the mdb would be to ... > provide RWXD permissions to the folder but RWX permissions to the mdb - ...
    (microsoft.public.access.security)