Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Reserved Error (-5001), there is no message for this error

Status
Not open for further replies.

milledj

Technical User
Jun 21, 2005
3
US
In the past two days when I try to open any of my databases I receive the following error message "Reserved Error (-5001); there is no message for this error". Does anyone know what this error means and how to fix it?
 
It would help to know a little bit more about your problem.
1. We assume this is MS-Access? Which version?
2. Does your database(s) have a 'StartupForm', or some macro that is executed on startup?

Meanwhile, what happens if you create a blank database, then link to one of the tables in the 'bad' database, then try to open the table? Do you get the error?

35+ years of 'progress' -- can't we all just go wire boards again?
 
Trevil,

It is MS-Access 2000 (9.0.3821 SR-1)
The database does start using an Autoexec Macro to open a Form. Currently, everyone else on our network who logs in to Novell can run the database. However, when I use my Novell login, the database will not work and I get the error that I mentioned.

When I created a blank database and linked to a table in the bad database, and opened the table in the new database I get the following message "Unkown".
 
My first guess would be that you have *lost* your rights somewhere in the path. If no other user has the database open, you will need create / write etc. permission on the folder where the database is stored (will create LDB file).

If you hold down the shift key to bypass the startup macro, can you open the database? If not, it's probably your rights. If yes, then are the tables located in that database, or are they linked to that database? If linked, I expect some level of authentication is hosed up.

35+ years of 'progress' -- can't we all just go wire boards again?
 
Thanks for your help, I think we found that it is a Novell Login issue and not an Access issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top