Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Compatibility with Access 97 ?? 1
- Thread starter Kbcca
- Start date
-
1
- #2
- Thread starter
- #3
Thanks CClint.
My application was originally written to work with Access 97 ( using DAO 3.51). Now I have changed the reference to 3.6 to be able to work with either Access 2000/2002. But there are some customers still using Access 97 ( and would like an upgrade of the application). Is there any way to avoid making multiple versions of my application ? Can I just give them the new version ( with DAO 3.6 ) to work with Access 97 ?
Thanks in advance,
Kb.
My application was originally written to work with Access 97 ( using DAO 3.51). Now I have changed the reference to 3.6 to be able to work with either Access 2000/2002. But there are some customers still using Access 97 ( and would like an upgrade of the application). Is there any way to avoid making multiple versions of my application ? Can I just give them the new version ( with DAO 3.6 ) to work with Access 97 ?
Thanks in advance,
Kb.
>Can I just give them the new version ( with DAO 3.6 ) to work with Access 97
Basically, yes.
Just do your developement/testing with the JET '2000 dbms using the DAO 3.6 interface, but continue to use a JET 3/'97 mdb until all users are changed over.
JET 4/2000 brings some improvements and new methods that were not available under JET 3/'97, and some which are only available in combination with JET 4 and a 2000 MDB. So, avoid usíng them until the change over. And the best way to stay clear of them is to develop with DAO 3.6 and a '97 MDB.
You need to of course test thoroughly with DAO 3.6 and a '97 MDB, as there are some changes which may affect the outcome, such as JET 4 being ANSI 92 compliant. You may get some syntax errors in SQL statements if you didn't take care and enclose all table and field names in brackets.
And, using JET 4 with a JET 3 MDB will be alittle slower because of the Unicode conversions (to and from) which are needed.
You also have to make sure if there are any duplicate references to more than one DBEngine object, each with a different version, that either the priority is set accordingly, or you use the full name qualifier.
For instance: Your project references DAO 3.6 and also the MS ACCESS Object '97 Library, and the DAO 3.6 reference comes after the MS ACCESS reference, and you try to open a JET 4 MDB using just
Set db = DBEngine.OpenDatabase(...)
the it is the MS ACCESS '97 Object that will be referred to with the DBEngine, and this of course cannot open a JET 4 MDB, even when DAO 3.6 is referenced.
You would either need to make the DAO the first referenced object, or use the full qualifier:
Set db = DAO.DBEngine.OpenDatabase(...)
But, this should be clear anyways.
There are some other things to take care for, but, as said, these will become evident if you thoroughly test your app using DAO 3.6/JET 4 dbms and a JET 3 MDB, and can be worked around.
Basically, yes.
Just do your developement/testing with the JET '2000 dbms using the DAO 3.6 interface, but continue to use a JET 3/'97 mdb until all users are changed over.
JET 4/2000 brings some improvements and new methods that were not available under JET 3/'97, and some which are only available in combination with JET 4 and a 2000 MDB. So, avoid usíng them until the change over. And the best way to stay clear of them is to develop with DAO 3.6 and a '97 MDB.
You need to of course test thoroughly with DAO 3.6 and a '97 MDB, as there are some changes which may affect the outcome, such as JET 4 being ANSI 92 compliant. You may get some syntax errors in SQL statements if you didn't take care and enclose all table and field names in brackets.
And, using JET 4 with a JET 3 MDB will be alittle slower because of the Unicode conversions (to and from) which are needed.
You also have to make sure if there are any duplicate references to more than one DBEngine object, each with a different version, that either the priority is set accordingly, or you use the full name qualifier.
For instance: Your project references DAO 3.6 and also the MS ACCESS Object '97 Library, and the DAO 3.6 reference comes after the MS ACCESS reference, and you try to open a JET 4 MDB using just
Set db = DBEngine.OpenDatabase(...)
the it is the MS ACCESS '97 Object that will be referred to with the DBEngine, and this of course cannot open a JET 4 MDB, even when DAO 3.6 is referenced.
You would either need to make the DAO the first referenced object, or use the full qualifier:
Set db = DAO.DBEngine.OpenDatabase(...)
But, this should be clear anyways.
There are some other things to take care for, but, as said, these will become evident if you thoroughly test your app using DAO 3.6/JET 4 dbms and a JET 3 MDB, and can be worked around.
- Thread starter
- #5
- Status
