Read/write Issues After Copying An Access .mdb File

[Jeigh]

I'm currently creating an interface program for a MS Access database. I've only used Access once in the past but used other DB's a handful of times so I didn't have any trouble getting the general program created. My issue arose when I tried to make it so that the users needing to use the program can just copy the .exe and the .mdb files and use it.

The program doesn't require users to share the database but to store their OWN programs information in their OWN database, so basically each needs to have their own database with the exact same design (but different data). The original plan was to just get them to copy over a near empty .mdb with the design set up and have them slowly create their own dataset with it. However, upon copying these files between my computer and others it ends up allowing my interface program to retrieve data from the DB but not write any new entries to it. All security permission on the file itself are set to allow read/write to everyone so I'm not sure what's causing this. Is there any other security settings I should worry about? Everything I could find within access seemed to be set so that it could be used freely so I'm not sure what the problem is. Any help would be greatly appreciated.

P.S. - I apologize if there is already a related topic in existence, I am new to these boards and tried to search beforehand for any information on this topic but came up empty handed so decided to start my own topic about this problem.

 

[The_Doc_Man]

You might be looking at an issue of a secured database that requires a login. The help files might help you build an unsecured copy of said .MDB file.

If the original was NOT secured and the users are making their own local copies, you could still be looking at a workgroup security issue. If they use other Access databases that ARE shared, they probably have to join a workgroup for them, too. But you can only join one workgroup at a time. To use a local database after using a shared one, you must find your SYSTEM.WKG file and rejoin it using the WKGPADM program (Windows /system32/ folder, if I remember correctly.)

 

[Jeigh]

Hm, neither of those seem to be an issue in the test case that brought this issue to my attention. I'll have to check into some things tomorrow. Thanks for the input though.

Any other ideas still appreciated

 

[Geoff Convery]

Have you tried setting the permissions manually on the files after they have been copied? It's possible that the "Everyone" you've given permissions to is actually the "Everyone" relating to your PC. In that case it's a different "Everyone" from the one on the target PC (annoying but sometimes true). The other way around it, if you have a Domain or Active Directory structure in your organisation, is to ask the Domain administrators to set up a "group" to which all the users belong and give that group read/write access to the file before you copy it.

 

[Jeigh]

We got a group set up with permissions and that worked... I can't see how that changed anything since they each individually had proper rights as far as I could tell, but regardless that worked. Thanks a million guys.