By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,052 Members | 1,456 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,052 IT Pros & Developers. It's quick & easy.

Access 2003 User Security ldb issue under Office 2010

P: 2
I have an Access 2003 application which is split. User level security is attached to the client as an .mdw. Both the client and .mdw files are copied to the user environment, with tables linked to the .mdb on the server.

The application had been running successfully for over two years, with monthly compacting and repairing. Now, write users seem to be limited to single access.

The application is running under Office 2010.
Recently, I noticed that, at execution, there are three .ldbs (two in the users local environment and one on the folder where the data is stored.)

I am wondering if this is caused by running under Office 2010 or due to something I did when the applicaton was moved.

I am planning to copy both the client and the server to fresh 2003 .mdbs and then re-input the security.

Any advice?
Mar 30 '12 #1
Share this Question
Share on Google+
3 Replies

Expert Mod 15k+
P: 31,494
I don't believe 2007 or later versions continue to support previous MDW based security at all Ted.

I usually expect the LDB file to be with the MDB in the same folder, and single-or multi-user issues covered by the Tools | Options settings rather than this.

Your use of the word "users" is entirely without apostrophes, so it's hard to get a clear indication of the details as you describe them (One user? Multiple users?).
Mar 30 '12 #2

P: 2
There are multiple users of the application who have been using it concurrently. I learned that if you open an Access 2003 database in Access 2010, you can still set user privileges (under the File option). The .mdw file works. In our application, some users only have read privileges; others have write, etc. In my case, the data resides in an .mdb in a shared network folder; a .bat file copies the client mdb and the mdw to a local folder on each user's workstation. The client is linked to the tables in the .mdb on the server. I suppose I will export each mdb to a new mdb and redo the security, but I was wondering if anyone else has had issues with user security in 2010 (running 2003). I did not check the locking options under Office 2010 and will do that tomorrow. Any other ideas?
Apr 3 '12 #3

Expert Mod 15k+
P: 31,494
I'm afraid I'm dry now Ted. I still use 2003 and can't run any tests even.
Apr 3 '12 #4

Post your reply

Sign in to post your reply or Sign up for a free account.