upgrade from A 97 to Acc 2000

  • Thread starter Thread starter Bob Barnes
  • Start date Start date
B

Bob Barnes

Your existing Front- & Back-ends are good.
Keep the "default" Access 2000 format in Access 2002
(should you need to use it with Access 2000).

In Access 2000, it defaults to ADO. Your existing DAO
code will need to Preface existing Objects like Recordsets,
QueryDefs, Parameters with. . . "Dim RS As DAO.Recordset",
etc.

Also, be sure to Check the Reference "Microsoft DAO 3.6
Object Library".

HTH - Bob
 
Bob Barnes said:
Your existing Front- & Back-ends are good.
Keep the "default" Access 2000 format in Access 2002
(should you need to use it with Access 2000).

In Access 2000, it defaults to ADO. Your existing DAO
code will need to Preface existing Objects like Recordsets,
QueryDefs, Parameters with. . . "Dim RS As DAO.Recordset",
etc.

Also, be sure to Check the Reference "Microsoft DAO 3.6
Object Library".
Click to expand...

Just to add to the above...

If you have a proper, error-free A97 app and use A2002 to *convert it* then
all of the references will be correct. The resulting file will NOT have a
reference to ADO, will have a reference to DAO, and you can choose whether
to implement library prefixing in your object naming.

However; if you create a new file in A2K2 and import all objects from the
app above, (a common practice when a file gets corrupted), then that file
*will* have the references wrong. It will now have an ADO reference that
at best will be unnecessary and at worst can break some of your code. You
would also be missing the DAO reference which would almost certainly cause
problems in an app that started life in A97.

You might also build a new app file from scratch in A2K2 and at some point
decide to re-use some code from your converted apps. Here again you might
see problems because of the default reference settings. In these apps you
might very well make use of both ADO and DAO and in these apps you will
definitely need to use the library prefix to avoid problems.
 
Back
Top