Upgraded Access, now can't access a DB

ELaJaunie

Registered User.
Local time
Today, 14:46
Joined
Sep 2, 2003
Messages
11
This one is a strange one to me, and I hope you guys can help me out here. I upgraded my old version of Access (which was 2000) to Access 2003. Now I can't get into a database that I used to be able to get into with Access 2000 and Access XP. It tells me that I don't have the correct permissions. Another user trying to access the same database gets the same error, and I had upgraded her version of Access (which was XP) to Access 2003. We had someone else open that database for us, and he is running on Access 2000 and he didn't have any problems. There were no problems when we used Access 2000 and XP. But for some reason, 2003 won't let us into it. I've got full permissions to the database as far as our server is concerned, so I'm pretty sure it's an internal Access 2003 problem. I've tried converting it from the original format (which was Access 2000 format) to the 2002-2003 format, but that didn't help at all. Please help! I need this database because we're running some reports off of it (the reports are in a separate .mdb file and need this particular .mdb to run the reports).
 
I am guessing that maybe the users PC was joined to a secured workgroup?

A PC should not be "joined" to a workgroup for odvious reasons [maybe yours] for you should use a custom shortcut to open the db with the correct version of Access and to also use the correct workgroup file.

Find and open the workgroup administrator program on the computer that does not have the problem and verify where and what workgroup file it is pointing to.

The workgroup administrator program is usually located at C:\Windows\System32\WRKGADM.EXE on a Windows XP PC.

The default workgroup file is the System.mdw file which is located in the same directory as the admin program. The default workgroup file is the System.mdw file should not be altered! You should create and use a new workgroup file if you are messing with security.
 
Well, the thing is, we've never set up any secured workgroups here. We just use the database as it is given to us and it just started doing this after the upgrade.
 

Users who are viewing this thread

Back
Top Bottom