[AccessD] Converting Access 97 to Access XP FE& BE

Thanks Charlotte.

I have Speed Ferret and will use that to find all instances.  

Greg Smith 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, March 10, 2004 3:12 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Converting Access 97 to Access XP FE& BE

Unless you're planning on using ADO exclusively, DAO works just fine in XP,
and you still have to fall back on DAO for somethings anyhow.  XP has no
problem with either CurrentDB or CurrentProject, and there is a certain
basic support for both ADO and DAO built into XP even if you remove *both*
the references.  I recommend you go through and specifically change your
declarations throughout to DAO.Recordset, DAO.Database, etc., both to remove
any confusion the engine has and to make it easier to spot them in your
code.  There are certain objects that have the same name in both models, and
without the specific declaration, Access can get them mixed up and think
you're trying to use an invalid method or property.

Charlotte Foust

-----Original Message-----
From: GregSmith at starband.net [mailto:GregSmith at starband.net]
Sent: Wednesday, March 10, 2004 11:48 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Converting Access 97 to Access XP FE& BE


Hi Everyone...again.

I have no clue what happened to that last message....Sometimes fast
computers can be a great disadvantage...sorry 'bout that.

I'm in the process of converting a rather complex Access 97 database (FE
is about 8 meg, BE with data is about 500 meg) to Access XP (or 2002 if
you prefer).  This is also a tightly secured database, using access's

<etc.>