Cannot open access MDB with runtime version when already opened in full version

H

Henri Visser

Hi,

I have an issue with an Access mdb on a network drive where a few users use
Access 2003 runtime version to open the mdb and a few users use Access 2003
professional (full) version to open and work with the mdb.

If the first person to open the mdb in the morning is one of those using the
runtime version, there are no problems and enayone else can open the mdb.

If the first person to open the mdb in the morning is one of those using the
full version, nobody using the runtime version can open the mdb.

I have read somewhere about splitting the mdb into a front and back end, but
I don't want to do that at this point in time.

Any suggestions welcome and appreciated.
Thanks
Henri Visser MCSE 2000
 
L

Lynn Trapp

Check the folder permissions on the server for your users. All of them need
to have Full Permissions to the folder.

Why do you not currently want to split your database? You are asking for
trouble if you don't do that.
 
H

Henri Visser

Shared folder is on FAT drive on NT server, so NTFS permissions do not
apply.

Share permissions has the "Everyone" group with Full Control assigned to it.
No other groups or users assigned share permissions.

The reason why I am not splitting the mdb at the moment is the same reason
why most things that should be done never is, INTERNAL POLITICS.

Thanks anyway.
-Henri
 
L

Lynn Trapp

Well, then, when the users have a problem opening the database is there some
error message generated?

You should tell one of your high muckety-mucks that their "internal
politics" may cause their data to be corrupted one of these days.
 
A

Albert D. Kallal

As mentioned, you uses do need full permissions to that folder.

In addition, they also need file DELETION rights, and file CREATION rights.
ms-access creates locking files to handle multi-user mode in the shared
folder (since there is no database server to handle record locking and
collisions, then ms-access creates files that each instance of ms-access can
"look" at to handle record locking). Thus, if users can't delete, and create
files in the shared folder, then ms-access has to operate in single user
mode.

So, make sure users can both create, and delete files in the shared
folder...

Also, make sure that users don't open the file in exclusive mode, as again,
that can prevent multi-user mode.
 
H

Henri Visser

NTFS permissions don't apply since it is located on a FAT network drive.
Share permissions to folder = Full Control to "Everyone" Group

Nobody is opening the mdb in exclusive mode as far as I can tell, because
when it is opened for the first time first in the full version, other users
using the full version can still open and work with the mdb as well, only
users using the runtime version cannot open the mdb.

As a test of permissions, I created a blank txt file from one of the clients
in the shared folder, then made some chnges to it, then saved it, then
deleted it, and it worked fine.

The clients with runtime version CAN open the file if it has not been opened
by a client with the full version first in the morning. So this lead me to
know that it can't be a Windows or network permission issue, but some kind
of Access permission issue.

Thanks
Henri
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top