Converting 97 to 2002

  • Thread starter Thread starter wysiwyg
  • Start date Start date
W

wysiwyg

(Originally posted in .multiuser w/o reply.)

When I try to convert my database (which has not been split) I am prompted
to select a new name. Will all of my security information - users, groups,
rules, etc. remain intact? Are there any "gottcha's" that I should be
aware of?

I have been google-ing, and some posts suggest de-securing the database
prior to conversion. Is this necessary? If so, what steps do I take?

Thank you!
 
wysiwyg said:
(Originally posted in .multiuser w/o reply.)

When I try to convert my database (which has not been split) I am
prompted to select a new name. Will all of my security information -
users, groups, rules, etc. remain intact? Are there any "gottcha's"
that I should be aware of?
Click to expand...

The conversion should retain your permissions, but you can of course double
check once it's done.
I have been google-ing, and some posts suggest de-securing the
database prior to conversion. Is this necessary? If so, what steps
do I take?
Click to expand...

That is the best approach. Open it in 97 logging in as a member of the
Admins group. Grant full permissions to the Users Group for all objects.
Exit Access, and reopen using the standard system.mdw workgroup. Create a
new database and import all the objects from yours. Then open 2002 and
convert this database. Then resecure using 2002.
 
Thanks Joan,

Once I create a new database & import all objects, will the users/group info
still be there with this method too, and I just have to set their
permissions back where I want them? Or will I need to re-enter all of the
original PID info, etc.?

What is the difference between creating a new database and importing all
objects vs. just making a copy of the original & then converting the copy?
I'm not sure I understand what all can go wrong by converting & that worries
me enormously!

I appreciate the help!
 
wysiwyg said:
Thanks Joan,

Once I create a new database & import all objects, will the
users/group info still be there with this method too, and I just have
to set their permissions back where I want them? Or will I need to
re-enter all of the original PID info, etc.?
Click to expand...

There are two aspects here. The users, groups, PIDs, passwords, group
membership are all stored in the mdw. Technically you can use a 97 version
mdw with a 2002 mdb. The permissions are stored in the mdb.

Whenever you import objects from a secured mdb, the object loses its
permission. Even if you aren't converting it. Just importing will do it.
What is the difference between creating a new database and importing
all objects vs. just making a copy of the original & then converting
the copy? I'm not sure I understand what all can go wrong by
converting & that worries me enormously!
Click to expand...

David has confirmed that if you convert using the builtin conversion tool
(Tools, Database Utilities, Convert), the permissions will not be lost i.e.
the conversion tool takes care of it for you. If you create a new database
and import, you *definitely* will have to reapply the permissions. You
could use the code at www.daiglenet.com - somewhere on the Access page
you'll see dbutilities, which will script out the permissions for you.

I would suggest you
1. backup your database as is
2. try converting it using the conversion tool
3. if you don't like the result, you can go back to the backup and try the
other route.
 
Back
Top