Converting From Access 97 to 2000 (Access 2000)

Topic

New Reply

If anyone could help it would be greatly appreciated.
We are currently working on converting to Access 2000. With that it takes time and unfortunately everyone else in the company wants to keep working. We have a ton of databases that need to be just opened in 2000 so that the people who are still using 97 can use them. In the documentation that I read it said upon first time opening in 2000 you will get the convert or open screen. That is easy, we went into the databases and opened them in 2000 so that everyone could continue on. Well once in awhile we are getting that same screen, convert or open and since you need to have the database exclusively in order to do anything the first time in 2000 that is not possible. Any ideas what is triggering the system to send that screen again?

Any other helpful hints for this conversion process would be appreciated.

Thank you,
Kristen

Reply | Quote

Replies

I don’t understand. Did you convert a copy of those databases or are you just opening them in 2000? Are these split front-end/back-end databases?

Reply | Quote

I am just opening them in 2000. These are not front-end back-end databases.

Reply | Quote

Then be prepared for problems. I’ve seen databases “stuck” between versions, not allowing design changes in 2000 but unable to be opened in 97 any longer. As for your original question. The most likely reason is that the database design was modified in 97 so that 2000 asks you once more about converting.

I’d highly recommend that you get *everyone* into 2000 ASAP. The kind of “sharing” you’re doing has been tried over and over, and it is extremely hard to maintain successfully.

Reply | Quote

One problem you’re likely to run into is that 2K expects to use ADO by default; 97 expects DAO by default. You have to add a reference to DAO if you’re doing any code to speak of.

As I recall, this one bites you as soon as you make a change and recompile, and the error messages you’ll get give you absolutely no clue why the music stopped. An innocuous line of code like “Dim rs as recordset” all of a sudden stops working.

Reply | Quote

That only happens on new databases where you import old code. Converted databases have the DAO reference set automatically. New 2000 databases have the ADO reference set by default and no DAO reference.

However, it’s a good idea to go through your code and replace all statements like Dim dbs As Database to Dim dbs As DAO.Database, etc., just to keep the compiler from getting confused. There are enough objects in the two models with the same names but entirely different methods and properties, so that it will save your sanity if you get used to specifically declaring objects as belonging to one or the other object model.

Reply | Quote