Strip Workgroup Permissions

I have been trying for most of the day to convert an access database from 97 to 2003 and I'm not getting anywhere.  When I open the file I get the message: "The current user account doesn't have permission to convert or enable this database".  I have tried joining the workgroup as administrator but this hasn't worked.

So... I opened the file up in 97 and gave the admin account full permissions on everything.  But this didn't work either. =(

Is there any way of completely removing the workgroup permissions?  I would import the objects rather than converting the file but I'm getting errors doing it that way.

Thanks in advance.
LVL 2
PsychotextAsked:
Who is Participating?
 
Kelvin SparksConnect With a Mentor Commented:
Can you try exporting from the old database to a new empty database (also 97)
0
 
Kelvin SparksCommented:
Login using Access 97 as the administrator. Close the old database leaving Access open (so you're still logged in as the administrator person). Create a new blank 97 database & try and import all the objects from the old database.

This should create a databse that you "own". You should now be able to convert this using Access 2003. THius method will require you to re-estbalish the security in 2003 if you need it. You'll need to play around with it, if you still need the security - it's acomplex issue to get right and you need to follow the established rules.


Kelvin
0
 
PsychotextAuthor Commented:
I'm not so worried about re-doing the security, but when I try to import I get all sorts of error messages like "Network or disc error" and "$table" could not be found.
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
Kelvin SparksCommented:
The network/disk one tends to be a hardware problem - server playing up or similar.

I'd be very cautious about the environment. You could try using another PC, I struck a dud one once when migrating one database to a leter version - created all sorts of havoc.
0
 
PsychotextAuthor Commented:
Tried it on a couple of machines... same error.  I don't think it's hardware.  It is kinda odd.
0
 
PsychotextAuthor Commented:
Not tried that yet.  Will give it a go.
0
 
Kelvin SparksCommented:
The other thing you should do, and we should have done this first up, is to compact & repair the original database.
0
 
PsychotextAuthor Commented:
Seemed to do the job, thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.