Compact and Repair with Access 2003 Runtime

ExpandCollapse

Guest

We have an app that currently uses the Access 97 runtime. We are working on
updating it to use the Access 2003 Runtime. One issue I have run into at one
of our Beta sites is Compact and Repair. I wrote a VB utility to do Comapact
and Repair for the A97 app. I used the DAO360.DLL library. One of the
functions I included in the utility is a Rebuild function. It's purpose is
for those rare occasions when the CompactDatabase method can't repair a
database - it creates a new, blank database, recreates all of the tables and
indexes, then copies the data from the original (similar to the method of
creating a blank DB and importing everything from the old DB if you have the
full version of Access). The problem is the CreateDatabase method, which
accepts a constant for the version, only has constants for versions up to
dbVersion30, i.e., Access 97 format. That seems pretty odd for a Jet 4 DLL.
CompactDatabase, in fact, which allows for converting the Jet version of a
database, also only supports up to dbVersion30. Fortunately CompactDatabase,
with no version supplied, doesn't change the current version, and it does
work on an A2K3 database. Does anyone have any suggestions? Is it possible
to create a new database using the A2K3 Runtime e.g. from the command line?
For that matter, where can I find a list of command line parameters for the
A2K3 Runtime? TIA!

ExpandCollapse

Guest

Are you sure you are using DAO360 ? It sounds more like you
are using
createobject("dao.dbEngine")
or some other Jet 3.0 object.

There certainly is a value for dbVersion40. if you use the correct library.

(david)

"Ron Hinds" <__ron__dontspamme@wedontlikespam_garageiq.com> wrote in message
news:%23BLPBkHdGHA.3556@TK2MSFTNGP02.phx.gbl...
> We have an app that currently uses the Access 97 runtime. We are working
on
> updating it to use the Access 2003 Runtime. One issue I have run into at
one
> of our Beta sites is Compact and Repair. I wrote a VB utility to do
Comapact
> and Repair for the A97 app. I used the DAO360.DLL library. One of the
> functions I included in the utility is a Rebuild function. It's purpose is
> for those rare occasions when the CompactDatabase method can't repair a
> database - it creates a new, blank database, recreates all of the tables
and
> indexes, then copies the data from the original (similar to the method of
> creating a blank DB and importing everything from the old DB if you have
the
> full version of Access). The problem is the CreateDatabase method, which
> accepts a constant for the version, only has constants for versions up to
> dbVersion30, i.e., Access 97 format. That seems pretty odd for a Jet 4
DLL.
> CompactDatabase, in fact, which allows for converting the Jet version of a
> database, also only supports up to dbVersion30. Fortunately
CompactDatabase,
> with no version supplied, doesn't change the current version, and it does
> work on an A2K3 database. Does anyone have any suggestions? Is it possible
> to create a new database using the A2K3 Runtime e.g. from the command
line?
> For that matter, where can I find a list of command line parameters for
the
> A2K3 Runtime? TIA!
>
>
>

ExpandCollapse

Guest

Thanks David - you were correct. Apparently the problem has something to do
with my help file - when I brought up help for CreateDatabase it only showed
up to dbVersion30 as an option. But just now I used the Object Browser and
sure enough, dbVersion40 is specified there. Thanks again!

<david@epsomdotcomdotau> wrote in message
news:%23f9uxxIdGHA.380@TK2MSFTNGP04.phx.gbl...
> Are you sure you are using DAO360 ? It sounds more like you
> are using
> createobject("dao.dbEngine")
> or some other Jet 3.0 object.
>
> There certainly is a value for dbVersion40. if you use the correct
library.
>
> (david)
>
> "Ron Hinds" <__ron__dontspamme@wedontlikespam_garageiq.com> wrote in
message
> news:%23BLPBkHdGHA.3556@TK2MSFTNGP02.phx.gbl...
> > We have an app that currently uses the Access 97 runtime. We are working
> on
> > updating it to use the Access 2003 Runtime. One issue I have run into at
> one
> > of our Beta sites is Compact and Repair. I wrote a VB utility to do
> Comapact
> > and Repair for the A97 app. I used the DAO360.DLL library. One of the
> > functions I included in the utility is a Rebuild function. It's purpose
is
> > for those rare occasions when the CompactDatabase method can't repair a
> > database - it creates a new, blank database, recreates all of the tables
> and
> > indexes, then copies the data from the original (similar to the method
of
> > creating a blank DB and importing everything from the old DB if you have
> the
> > full version of Access). The problem is the CreateDatabase method, which
> > accepts a constant for the version, only has constants for versions up
to
> > dbVersion30, i.e., Access 97 format. That seems pretty odd for a Jet 4
> DLL.
> > CompactDatabase, in fact, which allows for converting the Jet version of
a
> > database, also only supports up to dbVersion30. Fortunately
> CompactDatabase,
> > with no version supplied, doesn't change the current version, and it
does
> > work on an A2K3 database. Does anyone have any suggestions? Is it
possible
> > to create a new database using the A2K3 Runtime e.g. from the command
> line?
> > For that matter, where can I find a list of command line parameters for
> the
> > A2K3 Runtime? TIA!
> >
> >
> >
>
>

Share This Page

Major General Patrick Sanders speaks about the importance of Sikhs serving in Her Majesty’s Armed Forces at the WW1 Sikh Memorial Unveiling event on Sunday 1st November 2015. Over 138,000 Indian troops fought in Belgium and France during World War I, many of them Sikhs....

About Us

Our community has been around for many years and pride ourselves on offering unbiased, critical discussion among people of all different backgrounds. We are working every day to make sure our community is one of the best.

Like us on Facebook

Support SPN

The management works very hard to make sure the community is running the best software, best designs, and all the other bells and whistles. We'd really appreciate your support!