Converting 97 to XP 2

[pullingteeth]

Hello, the company I work for is moving to an XP platform; the database I maintain won't work using Access 97 under the XP installation without the VB6 runtime, which the company is reluctant to include as part of the base rollout. So, I'm having to convert it into Access XP.

The built in Access importer failed on a RecordSet declaration; I bet it wanted me to declare it as an ADO object. However, I know that DAO can be used in Access XP (right?), and therefore don't want to change.

So, I imported all of my forms, tables, etc, and now am hitting a new problem: it doesn't seem to mind the RecordSet declarations any more, but it objects to dbOpenDynaset, dbOpenSnapshot, etc in the OpenRecordset function calls ("variable not defined").

Do you know any way around this?

Thanks

 

[PHV]

While in VBE, menu Tools -> References ...
Check the Microsoft DAO 3.6 Object library and move it up, before the ActiveX Data Object library.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[pullingteeth]

Thanks PHV.

Am I going to have to do this for each and every user I roll the database out to? Or at "compile" time, is this included?

 

[RoyVidar]

If you're "rolling e'm" out by giving each user a new copy, it should suffice with doing it once in the version you're developing on, prior to deploying (though I'm not 100% sure the order of the references will always be "correct"). In other words, my view is not to rely on the order of the references, but take it a step further.

To disambiguate completely, I'd suggest finding every declaretion of DAO objects, and disambiguate them by prefixing with library:

[tt]dim rs as dao.recordset
dim db as dao.database
dim qd as dao.querydef
...[/tt]

Roy-Vidar