Converting Access 2.0 to 2003...

[Vagabond Software]

Yesterday, I tried converting an Access 2.0 database file to Access 2003,
without success.

I followed the instructions from the Microsoft web-site for converting
Access files from a previous version:
http://office.microsoft.com/en-us/assistance/HP051863781033.aspx

There are a ton of forms, reports, and especially macros, but there is only
one module. I selected Compile Loaded Modules from the Run menu and saved
the database.

When I attempt to open the Access 2.0 database in Access 2003, I am prompted
to convert it. I choose to convert it and save it an alternate folder with
the same database name. I am then informed that I need to install the
Access 2.0 Converter, but it is already installed. I have now had that same
problem on-site and here in the lab.

Since I successfully converted Access 97 databases to 2003, I decided to
attempt to convert the Access 2.0 database to Access 97. Again, I am
prompted to convert the database. I agree and choose an alternate location
on the disk with the same database name. After some items are successfully
converted, I get the following error message:

"There were compilation errors during the conversion or enabling of this
database. The database has not been saved in a compiled state."

Sure enough, when I open the database in Access 97 and click a button on the
main form, I get a compile error "Sub or Function missing". Indeed, the
offending Sub-routine that is called is, in fact, not defined.

Any help or advice is greatly appreciated.

carl

 

[Albert D.Kallal]

Since I successfully converted Access 97 databases to 2003, I decided to

attempt to convert the Access 2.0 database to Access 97.

Great idea. I was going to suggest the above. Remember, access 97 is about 9
years old.

And, access 2 is now 12+ years old. Try to think back what the computer was
like 12 years ago.

Again, I am prompted to convert the database. I agree and choose an
alternate location on the disk with the same database name. After some
items are successfully converted, I get the following error message:

"There were compilation errors during the conversion or enabling of this
database. The database has not been saved in a compiled state."

The above makes perfect sense. 12 years ago, computers were just starting to
commonly have a mouse...let alone a GUI.

It is quite stunning that you can convert the applation.

And, it should be little, or no surprise that the code has some compile
errors. In fact, it is VERY possible that the access 2.0 application had
compile errors!!!

As a user of ms-access, you want as a general rule when you developing
things to OFTEN COMPILE the code to check for errors.

In your case, you now have a a97 application. While looking at code, you
want to do a debug->compile...and fix code errors one by one..

(the conversion process can't always convert such old code......).

Sure enough, when I open the database in Access 97 and click a button on
the main form, I get a compile error "Sub or Function missing". Indeed,
the offending Sub-routine that is called is, in fact, not defined.

As mentioned, this compile error might actually exist in the original.

Does the original 2.0 compile in access 2?

If you don't have the old system 2.0, then this is going to be more
difficult. However, what is the name of the sub...or can you tell in the
context of the code what the routine is supposed to do? Is this a built in
sub...or a user defined one?

further, do you have experience working with code in ms-access? (if you
don't...you might want to enlist local help...as a experienced access coder
can likely tell you what is the real problem in 5 minutes of time..).


I would also check the references issue also...

 

[Guest]

You can look in MSACCESS.INI to see what references
your version 2.0 application had loaded.

Or if you tell us what Sub or Function is missing, we might be
able to tell you where to look.

(david)