Converting from Access '97 to 2000/2002 1

[RichardBott]

I have an Access 97 application that is split between its code and database. I am having difficulty in converting it to Access 2002. I would like to convert both the database and the application. When I startup the application under Access 2002, it asks if I want to convert. I choose this option and a new name for the database but after conversion it reports that a series of errors occurred. These errors point to the access 97 database, not the 2002 one just created. They state that Access was unable to refresh the linked tables.

Is it possible to convert a 'split' '97 application? If not or if it is easier, can I re-combinme them in Access '97? I can do this in Access 2002.

Thanks for any help you can give.

 

[lamarw]

Yes, you can recombine them into the 2002 database simply by importing from the split database. This will retrieve all the tables. However, you might try converting the split tables to the 2002 format before you convert the code.

Lamar

 

[RichardBott]

Thanks for your response Lamar. I have tried to import from the split database/application but get conversion errors stating that Access was unable to refresh the split database tables (I have some tables in the application .mdb and some in the database .mdb). The database .mdb reported was the pre-converted database, not the new converted database I had created!

Any ideas?

Richard

 

[lameid]

In Access 97 before converting, compact both databses.
Use the Decompile switch to remove all compiled states from both files (msaccess.exe DatabasePathAndName /decompile). Compact both databases.

Try converting each file. Access 200X should be able to link to the ACC97 Backend just fine.

If this doesn't help, post the exact error message text here.

 

[RichardBott]

I tried to run the decompile but Access could not find the database file. I verified the spelling a couple of times. I ran the command from within a DOS window having selected the folder that the database was in. Should I have run the command from the folder that msaccess was in and specified the full pathname for the database? Is the 'decompile' option not available from within interactive access?

Can I run this command using the 'run' command? If so what about msaccess and database path names?

Richard

 

[RichardBott]

A further update re the problem I am having.

I followed lameid's advice exactly this time running msaccess.exe twice (once for the application .mdb and once for the data .mdb) to do the decompile in the folder in which it is located and referenced my .mdb qualified by the path. It worked!

But I am still having a problem converting the 2 .mdb's.

First of all, I converted the database .mdb - that is the file with all of the server-type tables in it. That appeared to work OK. I named the output IFTS_Data_2002.mdb.

Before I tried to convert the application .mdb, I renamed the original access 97 database mdb to include a suffix of _97 so that the application would not open it, but instead, ask me for the name of the database .mdb.

I then opened the application .mdb in Access 2002. I selected convert and specified an output of IFTS v1_02_2002.mdb (the original being IFTS v1_02.mdb). The application .mdb also has some tables in it - these are tables that are specific to the user.

I then got the following info/error messages.

Since I cannot figure out how I can submit copies of the actual info and error dialog boxes, I will state the contents:

Info Message: "MS Access encountered one or more errors during conversion. To view a summary of these errors, open the 'Conversion Errors' table." When I try to open the IFTS v1_02_2002.mdb in access to see this table, after choosing the .mdb, I get the following error:

Error Message: "IFTS Data file could not be found. You can use the next dialog box to find the file...." When I click OK, a dialog box appears but the "Files of Type" is just "IFTS Data File" and all folders are empty!

I do not understand where the "ITFS Data File" file type comes from. This is not an application that I wrote, I am simply trying to convert it from Access 97 to Access 2002.

Any help would be much appreciated.

Thanks,
Richard

 

[KenReay]

Hi

Are you absolutely sure that the Access97 version is free of comile errors before you start? check this out by opening the Access97 version, open a code module and select Comile from the menu, fix any compile (syntax) errors reported, and repeat until no errors are reported.

Do you have an autoexec macro or other "start up" mechanism to display the first form, if yes, disable them in the Access97 version.

Now try converting the Access97 FE to Access2003, is it successful?



Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[RichardBott]

I'll check that out Ken. What is the Access97 "FE"?

Richard

 

[KenReay]

hi

(F)ront (E)nd, ie the mdb with your forms, reports, queries, and code in it

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[RichardBott]

Ken, you gave me a clue when you mentioned "start-up" code. I looked through the modules and found one that guided the user through locating the database if the app could not find it. That was the source of the "IFTS Data File" message I referred to above. When I re-tried the conversion, I was careful to keep the server database - BE - filename the same for the FE conversion. And it worked!

Thanks to you and others who have helped with this. I very much appreciate it!

Richard