97 to 2002 updating question

[paulhh]

At work I have inherited upkeep on a 97 access database and we plan to convert to office 2002 and want to "upgrade" the database.
Thankfully in the "query" forum they helped me with references problems but it opened my eyes to another potential issue.

One of the references was msiav.ocx which apparently is a WIN98 Active X control. (Every reference when I did a web search was to Win98) I was able to pull it into XP and run the database but there must be something else newer to replace it and run properly under XP. Does this have something to do with the "DAO" / "ADO" discussions I was trying to follow in the group?

Would appreciate any help in this regard.

Paul

 

[The_Doc_Man]

Since I don't have an XP to play with, I can only suggest some common principles. If the AC97 version is properly installed, you can open up a module window (got to be able to see code for this) and take MenuBar path Tools>>References.

The list of files you see there is all of the .DLL, .TLB, and .OCX files (and others, too!) that Access can see. The checked ones are all the ones you or someone else told it to use. Some are pretty much hard-wired. Others might have been put there by whoever had this DB before you.

For example, look at the DAO entry in that list. It is probably either of DAO2535 or DAO351 for AC97. For AC2K, it is DAO36. Got no clue for XP, but it won't be a lower number than 36.

The same concepts will apply to most if not all of your library references. The first part of the names will likely be the same but the numeric part (representing a version number) might be different.

Tedious though it may be, you could step through that list and browse through your windows\system32 directory plus your office directory to find each of the files affected. Then open an explorer window to see if a newer file of the same type exists in the same directory. That might help you with finding newer references than the ones you are currently using.

Hope that made sense to you.

 

[paulhh]

Thanks DOC MAN,

There are only 5 files in References.
1. Visual Basic for Applications
2. Microsoft Access 8.0 Object Library
3. Microsoft DAO 3.51 Object Library
4. MSInfo MSIAV Category Module
5. Microsoft Calendar Control 8.0

So will try swapping them out.
As noted before couldn't find MSIAV on system or even Internet other than Win98.
Other strange thing, Thursday on my Access 97 the Calendar Control 8.0 showed missing and I had some Calendar problems so I found the Calendar and the "missing" went away and so did my problems. Today "Saturday" came in to work and got your message and The Calendar Control 8.0 doesn't show anymore but my problems are still gone. Weird.

Probably should have mentioned am running the Access97 on a Win98 machine and the Access2002 on an XP Professional machine for conversion testing.

Paul

 

[The_Doc_Man]

One of the issues commonly involved here is that references are in your registry plus they appear in the COM of your database, in the Application.References collection. As a debugging thing, if you are having trouble with references, you can write some simple code to dump the current reference list to a table or a file under some circumstances. Or just do a Debug.Print of them so they show up in the bottom part of the debug Locals window.