secure access 2.0 database that needs to be converted to access 20

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Okay, I have a bit of a trickly situation.

I think I mentioned this before, but did not get a good answer that solves
my problem. The database was created long before I started at the company.

Basically the database was created in access 2.0 to store customer data and
sales data. The tables were created under the administrator user id from
what I can tell. Various user accounts were created to input and or update
information.

The database was then opened and used in an access 97 database. However the
access 2.0 database was never converted from an access 2.0 database to an
access 97 database. I tried to open the database in access 97 in exclusive
mode, but I get an error saying that you don't have the permission to do so.

I opened the database back in access 2.0 and I was able to access the
database as it was, no errors or anything. I tried to add the permission to
open the database exclusively to the existing or orginal database as it was
created, but I don't have the permission to do this even in access 2.0.

As I said before, the database was created as admin, or administrator,
either which id I could not figure out the password. Is there a way to
switch the owner's of the tables and or the database so I can get access to
the database and be able to open it exclusively in access 97 and evenutally
into access 2000 so I can convert the entire database from access 2.0 to
access 97 or even access 2000.

In either case, I need to log in as the correct database owner and grant
open exclusively (is this correct). How can I get around the password
situation?

What else can I do to make sure that I can log in and grant the permissions?
Could I add a user to the admin group? Any answers would be of help.

Edward Letendre.
 
If you can open the Access 2 database in Access 97, and open the tables
from the Tables tab, and see the data in those tables, then, you should
just create a new database in Access 97, and use File:Import (or
whatever it is) to copy the data from the Access 2 tables, into the
(new) Access 97 ones. Then archive the Access 2 database, & continue
with the Access 97 one.

HTH,
TC
 
actually I have been trying to recreate the database in access 2000, but I am
stuck at the part about creating the forms and reports as there are many
forms and reports that I would have to re-create. Have you ever tried to
convert a database from access 2.0 to access 97? What permissions would I
need?

Edward Letendre.
 
I don't see the point in trying to "recreate" the tables & forms &
reports, if you can simply import them into a new database of later
format (97, 2000 etc.). I recomment that you focus on the "importing"
approach, rather than the "converting" one.

I've never used Access 2.0, but I believe it used an earlier version of
the VBA programming language, called "Access Basic". I think (but am
not positive) that Access Basic will still work in Access 97, but I'm
not sure about the later versions. You'd probably want to convert your
code from Access Basic, to VBA.

If the security restrictions in the old database stop you importing the
forms & reports, there was a big security hole in Access 2.0 called the
"copyobject flaw". You could probably use that flaw to retrieve the
forms & reports. Google for "copyobject flaw" & you will doubtless find
more information.

HTH,
TC
 
I have been trying to export various objects from access 97 (with the access
2.0 opened in access 97) and then import the objects (ie: a form) into
access 2000 in the newly created database. I have infact re-created all of
the objects except for the reports and the forms. I am working on tacking
down the correct passwords in access 2.0 so I can try and get the permissions
changed to be able to open the database exclusively in access 97 and or
access 2000.

I guess my major problem is the fact that even if I can access the original
database in access 2.0 and access 97, I cannot get into the database in
access 2000 as the user accounts and groups have not been setup in access
2000 as of yet. Is there any tools that I can access within access 2.0 that
will allow me to see the user accounts and groups that need to be created in
access 2000? I tried the printout user accounts and groups within access 97,
but I got an error saying that the groups don't exist. I know that the users
have been added to the mdw (or whatever the file is) through the admin group
tool for access 97 so that the database itself can be opened and accessed and
such. but again the problem is that you cannot open the database exclusively
nor can you change any priviledges in access 97 or access 2.0 without loggin
in as admin or ATSAdmin in the case of this database. Hopefully once I get
the correct password for the admin account and the ATSAdmin account (ATSAdmin
is the id that was used to create some of the tables and other objects as
well as atsinv account). I hope to have the whole database open exclusively
and convert it to access 2000.

At this point, I am still lost as to what to setup in access 2000 for user
accounts and groups once I roll out the database as an access 2000 project
(which is my final goal). If you or anyone can suggest where I should be
looking at to setup the correct user accounts and groups to even open the
existing database or any future databases, I would really appreicate it.

As the situation sets now, the users log into the database using the atsinv
account along with a known password and enter their data and such. In the
future, I hope to have the users log into an access 2000 project with the
original database converted or re-created as an access 2000 database and have
them log in with their own ids and access the data at their desktops under a
SQL server 7.0 database an an access 2000 front end.

But as I said before the main problem is the permissions (which I hope to
reset or setup up differently) once I get the admin password from the old
admin and get things rolling from there.

Any advice on what to do next in access 2000 or access 2.0 as to permissions
and accounts and groups to be added, created, etc. would be of great help to
me.

Edward Letendre.
 
You persist in wanting to convert the 2.0 database.

I suggest, again, that you try to imPort the 2.0 objects into a new
database of later format.

That is:

1. Create a new database of later format (eg. 97);

2. Use File:Get External Data:Import (or whatever it is) to *import*
the objects *from* the *unopened* 2.0 database *into* the *open*
later-format database.

As for recreating the previous users & groups, I suggest you get the
2.0 obects into a working later-format database, before you worry about
that.

HTH,
TC
 
TC is right, don't try to convert the access 2.0 Database to 2000, this wil
not solve your problem. There is no way to convert the original .MDW to 97 or
to 2000. You have to create it new. To do this you have to know all the
original AID and all PID's of all groups and users.

Your destination is a 2000-project, where all your data reside on
SQL-Server. Permissions for the data-tables you have to define on the
SQL-Server.
2000-projects work without any .mdw-file, security is different from mdb.

Import your all your database-objects in an unsecured 2000 database, try to
recompile your the code. Since 2.0 there are a lot of changes.

Before you will go on have look at
http://support.microsoft.com/?scid=http://support.microsoft.com/support/access/content/secfaq.asp

good luck

Gerlinde Kirse
 
Actually I have been fooling around with the conversion process as it is a
straight database (*.mdb). The conversion went okay as I tracked down a
program to get the passwords from the Access 2.0 database and from there I
was able to log into the database as an access 2.0 program to check the
permissions. The permissions were set correctly for the user id I wanted to
use to get the conversion done. I did get it to work on a test copy of the
database (a copy of the original file and I am successfully able to open the
database as a true access 97 application. I realize what you mean with
access 2000 as the conversion did not complete successfully as the old access
2.0 code that was used did not use generic calls, programming methods, etc.
But that is okay, as I can open the reports, forms, etc. as a true access 97
and access 2000 database. As for the security from access 97 to access 2000,
I re-created the users and groups from the information that I was able to
obtain in Access (by logging in as an admin or a user with admin
priviledges). I am working on setting up the security to have all users and
accounts active.

The one weird thing I could not get around was when I created a new admin
account, the same as it was in access 2.0 for access 97 on my own computer, I
could get the account to be created, but I could not add the same password as
before, I had to infact use a blank password to get the file to open.

At this point, I have a fully converted database and a database that is a
shell (the tables and modules are created, but the forms and reports don't
exist.

I am re-reading the security document to get things the same on both
computers for an access 97 and access 2000 application. I will work on SQL
server 7.0 (for the project part) once I have all the application working
successfully under access 2000. I am going to do this by gettting a user to
stress test the program to see if anything is broken or not working at any
point, but as I said, I can open the menus and the database appears to be
working at this point. I still have to add the rest of the users and their
permissions, but at this point it works.

If anyone can suggest what a next step should be to get things to work
smoothly for me, I would appreciate it. I know that the security part should
be the same and I will do that for all computers once I have it up and
running.

I am going to add a new message to the group in regards to multiple
databases on the same machine (different from this topic).

Edward Letendre.
 
Back
Top