Programmatically connecting to backend

[=?iso-8859-1?B?UultaQ==?=]

I have an odd issue, wondering if someone might have seen this. Not
sure whether this question is more appropriate here, in security, or
if this is a network administration issue - but here goes...

I've got a database split into front and back end. Back end is
password protected. The front-end has some code that prompts the user
for a password, and then links to the back-end. This was working
perfectly well at the client site, up until a few days ago.

They created a new folder on the server, and restricted access to only
users who are allowed access to the database. All of a sudden, only
one user at a time is able to be in the database - otherwise, it won't
connect. All users can access - so long as no one else is using the
database when they try.

It's almost as if the front end is now opening the back-end in
exclusive mode.

Has anyone seen this? Any suggestions? Server is Windows 2003, client
machines run Windows XP.

Regards,
Remi

 

[=?iso-8859-1?B?UultaQ==?=]

Found it:

Problem was they had not provided permissions to users to create files
in that folder, which means the ldb file wasn't being created, which
caused the data file to be locked exclusive.

Remi.

 

[Albert D. Kallal]

It's almost as if the front end is now opening the back-end in
exclusive mode.

Has anyone seen this? Any suggestions? Server is Windows 2003, client
machines run Windows XP.

Yes, we see this a lot, and 99% of the time it means the users were not
given full permissions to that dir. when we say full permissions, that
include file create, file delete...full means full rights.


Ms-access is a simple file share, and when you go mulit-user, ms-access
attempts to create a locking file (the ldb file). This fie is used for
multi-user..and managing conflicts. If ms-access can't create this file,
then it opens the database in single user mode...

So, those users likely don't have full permissions to that directory, and
each user needs full rights..and that includes file create, and file delete
rights. When the user runs their front end, and opens the back end...a
locking file is created in the SAME directory as the back end file. (so,
users must be able to create and delete files in that directory).