Problem with converting Access 97 Db to Access 2000

[Siobhan Perricone]

We're trying to convert the last Access 97 database in our department
to Access 2000.

The database is secured, and the problem is that the database owner
hasn't worked for the department for years. So his account has been
gone for a while, and the database no longer has an actual owner.

We have a couple of administrative accounts, and they've been able to
do what was needed to this point, but there are two tables over which
we can't seem to get administrative rights:

MsysModules
MsysModules2

Because we can't seem to get administrative rights to these two
tables, we can't convert the database.

Does anyone have any hints for a way to force the Db to give us
administer rights to these two system tables?

(We've tried importing the data objects into a new Access 2000 Db, but
it's breaking a lot of the forms, etc. I was hoping I could just get
it to convert so I wouldn't have to figure out why everything is
breaking when we import it.)

 

[Paul]

If you have rights on everything else, import all objects to a new database
and set security as necessary on THAT database.

--
Michael Badnarik for President '04
Libertarian...the freedom party
www.lp.org
www.badnarik.org

"If you are in prison and your chances are 50% for execution by electric
chair, 45% for execution by lethal injection, and 5% for escape, are you
just going to vote for the chair because it is the likeliest outcome?" Vote
Libertarian and live to be free.

 

[Joan Wild]

MsysModules
MsysModules2

Because we can't seem to get administrative rights to these two
tables, we can't convert the database.

You should not need permissions on these tables to convert to 2000. In fact
you should not be importing *any* of the Msys tables.

Just import all tables except these. They'll be created by Access.

It isn't necessary, but may avoid future problems for you, particularly
since the original owner of the mdb is long gone. I suggest you unsecure
the database in 97, then convert it, and resecure it in 2000.

 

[Siobhan Perricone]

You should not need permissions on these tables to convert to 2000. In fact
you should not be importing *any* of the Msys tables.

Tell Access that. It refuses to convert and the reason it gives is
because there are tables that I don't have admin permission on. When I
go to the Microsoft knowledge base, the solution is to give myself
administrator rights to all the system tables.

When I try to do that, it won't let me change for those two tables.
And it is only those two tables that I don't have administrator
permission on.

Just import all tables except these. They'll be created by Access.

It isn't necessary, but may avoid future problems for you, particularly
since the original owner of the mdb is long gone. I suggest you unsecure
the database in 97, then convert it, and resecure it in 2000.

The problem I'm having with importing all the tables over is that we
get a lot of errors when we then try to run the database. Probably to
do with security issues.

So I kept thinking that it'd just be easier to get it to convert than
to figure out why the import to a fresh Db isn't working. Maybe not,
though.

 

[Joan Wild]

The problem I'm having with importing all the tables over is that we
get a lot of errors when we then try to run the database. Probably to
do with security issues.

So I kept thinking that it'd just be easier to get it to convert than
to figure out why the import to a fresh Db isn't working. Maybe not,
though.

I'd open it in 97 and compile and compact it. Ensure that the system tables
are hidden (Tools, Options). Unsecure it, then convert it to 2000; then
resecure it. I have never had a problem with the Msys tables doing a
conversion.

What kind of problems are you getting 'when we then try to run the
database'?

 

[Siobhan Perricone]

I'd open it in 97 and compile and compact it. Ensure that the system tables
are hidden (Tools, Options). Unsecure it, then convert it to 2000; then
resecure it. I have never had a problem with the Msys tables doing a
conversion.

I have to admit that I don't know how to unsecure a database. I've
tried looking through help but I'm probably not searching for the
right phrases. Can you tell me how you unsecure it?

What kind of problems are you getting 'when we then try to run the
database'?

There's a form that opens up when the database starts up, and there is
a series of uninformative errors, one after the other, and in the end,
the form doesn't open up. I'll try what you suggest above first, then
if that doesn't work, I'll give this a go.

 

[Joan Wild]

I have to admit that I don't know how to unsecure a database. I've
tried looking through help but I'm probably not searching for the
right phrases. Can you tell me how you unsecure it?

Open it in 97, logging in as a member of the Admins Group.
Go to Tools, security, Permissions; select Groups and select the Users
Group.
Go through every object in the database (don't forget the database object),
and give full permissions to the Users Group.
Close Access.
Reopen Access using the standard system.mdw workgroup (you should get no
login).
Create a new mdb and import all objects from your's. This mdb will be
unsecured.
Compile and compact it.

 

[Guest]

I have the same problem and I tried your suggestions; all works fine with
tables and queries, but when I try import masks and reports I have an error
message: I, haven't the autorization for read data in MsysModules table.
Could you help me? Thank you.

 

[Guest]

I've setted the authorization on the MsysModules table, but now I have a new
problem: importing a mask I have an error regarding Index1. I Haven't this
index! I'm not the creator of this database, and I don't know what I have to
do. Listen: if I export the same mask in the new db from the old one, it
works ! But there are 150 mask, and I have to export them one by one !
Help me !