How to get VB app to generate Access 2003 databases with DAO?

[Robin]

Hi all,

I'm working with a VB app, using DAO 3.6, that used to generate Access
'97 databases using the following code:

Set dbsNew = wrkDefault.CreateDatabase(strLPAccessInv, dbLangGeneral,
dbVersion30)

I was able to have it create databases in Access 2000 by changing
"dbVersion30" to "dbVersion40". Do I generate a database in Access
2003 by changing the code to something like "dbVersion50" or do I need
to re-write the code in ADO or is there some other issue I'm not aware
of? The new databases consist of tables with data only, nothing else.

Thanks.
Robin

[Larry Linson]

The "Access" databases you are generating are, in actuality, Jet database
engine databases. The Jet database engine used by Access 2003 is the same
Jet 4.0 database engine used with Access 2000, so your "dbVersion40" ought
to work just fine. There have been eight (8) SPs to Jet 4.0, and I suggest
you make sure you obtain and apply all of them.

Larry Linson
Microsoft Access MVP

"Robin" <du**************@yahoo.com> wrote in message
news:19**************************@posting.google.c om...

Hi all,

I'm working with a VB app, using DAO 3.6, that used to generate Access
'97 databases using the following code:

Set dbsNew = wrkDefault.CreateDatabase(strLPAccessInv, dbLangGeneral,
dbVersion30)

I was able to have it create databases in Access 2000 by changing
"dbVersion30" to "dbVersion40". Do I generate a database in Access
2003 by changing the code to something like "dbVersion50" or do I need
to re-write the code in ADO or is there some other issue I'm not aware
of? The new databases consist of tables with data only, nothing else.

Thanks.
Robin

[Robin]

Larry,

Thanks very much for your advice. I checked, and it seems that I have
version 4.0.8618.0 (Security Bulletin MS04-014) of msjet40.dll -- so
I'm as current as I can get. Is what you're saying that by using
"dbVersion40" the code below should generate a database in Access2003
rather than 2000?

Thanks again,
Robin


"Larry Linson" <bo*****@localhost.not> wrote in message news:<jCF1d.5701$MS1.401@trnddc02>...

The "Access" databases you are generating are, in actuality, Jet database
engine databases. The Jet database engine used by Access 2003 is the same
Jet 4.0 database engine used with Access 2000, so your "dbVersion40" ought
to work just fine. There have been eight (8) SPs to Jet 4.0, and I suggest
you make sure you obtain and apply all of them.

Larry Linson
Microsoft Access MVP

[Larry Linson]

"Robin" <du**************@yahoo.com> wrote in message
news:19**************************@posting.google.c om...

Larry,

Thanks very much for your advice. I checked, and it seems that I have
version 4.0.8618.0 (Security Bulletin MS04-014) of msjet40.dll -- so
I'm as current as I can get. Is what you're saying that by using
"dbVersion40" the code below should generate a database in Access2003
rather than 2000?

No, what I was trying to say is that _Access_ is not involved in your
database in any way at all. VB interfaces directly to the Jet database
engine -- what you are generating is a _Jet_ database.

But, few of us, and especially Microsoft, are careful to draw that
distinction and often resort to the verbal shortcut of calling it an "Access
database".

Access 2000 uses Jet 4.0, to which all 8 SPs should have been applied.
Access 2003 uses Jet 4.0, to which all 8 SPs should have been applied. As
far as I know the "differences" between a database generated by Access 2000
and one generated by Access 2003 and saved in "Access 2003 format" are all
in the database objects: queries, forms, reports, macros, and modules, not
in the tables or the data itself.

Larry Linson
Microsoft Access MVP