ACCESS 2000, WINXP Pro Security distroyed, how to fix

  • Thread starter Thread starter Don Hobson
  • Start date Start date
D

Don Hobson

I have a rather complex database used to run a business.
It was designed and running under WINME with ACCESS 2000
and no security other than defaults. Recently bought a
new machine with WINXP and moved the database to the new
machine. After a while I needed to make form and SQL
changes and found to my dismay that I can't get
privileges to make any changes. Somewhere along the line
the OWNER was changed to <Unknown> and the Admin user has
no privileges to change anything. I am stuck. I tried
creating a new database as Admin but don't have
priviledge to import any object except the data tables
from the original database. Is there any remedy to
change the <Unknown> owner back to Admin in a way that
will allow setting permissions? (AND, NO, I don't have a
backup that hasn't been changed)
 
Don Hobson said:
I have a rather complex database used to run a business.
It was designed and running under WINME with ACCESS 2000
and no security other than defaults. Recently bought a
new machine with WINXP and moved the database to the new
machine. After a while I needed to make form and SQL
changes and found to my dismay that I can't get
privileges to make any changes. Somewhere along the line
the OWNER was changed to <Unknown> and the Admin user has
no privileges to change anything. I am stuck. I tried
creating a new database as Admin but don't have
priviledge to import any object except the data tables
from the original database. Is there any remedy to
change the <Unknown> owner back to Admin in a way that
will allow setting permissions? (AND, NO, I don't have a
backup that hasn't been changed)

On your old machine you also had a workgroup file with an MDW extension.
You need that file copied to the XP box as well and then you need to use
that MDW file to access the secured MDB either by making it your default,
or by specifying it as a command line argument.
 
Rick
Thank you for your quick response. The solution makes sense and is straight forward. However, I wish that I could do as recommended. However, there is a rather large problem: the old hard drive crashed and I don't have the drive to try and recover the file. Any other way around the security? I don't have copy, export or link privileges! I can link and import the data tables but then I can't change their definitions. Neither can I open/display the ACCESS Basic code to hand copy it! Even if I could recreate it that way, it would take at least 300 hours of work to open and hand type and retest all the code, queries, forms, macros and reports
Regards
Don
 
Back
Top