G
G-Man
I am using the FDUpdater tool to split Access 97 FEs and BEs. I am now
looking, finally , at the 2003 conversion of these databases. Setting the
actual conversion aside for now, I have an issue regarding the DAO when I use
a particular upgrade path. The situation below deals with the entire Office
97 and Office 03 install packages, but I am only focusing in on Access
On all boxes I am looking at (other than my test box, #3), it looks like
Access 97 was installed prior to 03.
Scenario #1 - On most machines, Office 97 was completely installed. Office
2003 was later installed, with the Option to NOT install Access 03 and to
leave Access 97. Default directories. On these machines, FEUpdater was added
and Access 97 FE/BE's via this tool have been operating just fine. You'd
expect this, because Access 03 was never installed in the first place. This
is where most machines are now. In addition, subsequently adding Access 2003
also seems to not harm the process.
Scenario #2 - There are also a few machines that were imaged slightly
different. On these machines, it *APPEARS* that with backward compatibility
in mind, these machines had Access 97 installed first, by itself (from the
Office 97 CD) and immediately had Office 2003 installed, complete - - - with
the option to KEEP Access 97 on the machine. But the directory location for
the 03 install was changed from the default Program Files\Office to Program
Files Office 2003
Again, these machines seem to operate fine in the FE/BE FEUpdater
environment opening Access 97 FEs.
Scenario #3 - But on a third variation test machine, I installed Office 2003
complete FIRST in it's default directory and then added Access 97 by itself
(with Spell Check). On this machine, when I try running the FEUpdater ini
for any 97 FE, I get a DAO error in the Auto FE Updater.
"The following error occurred while attempting to determine the Access/Jet
version of the file . . . . . (while using DAO Version 3.6). Error 3041:
Cannot open a database created with a previous version of your application."
I can manually open an Access FE without any problem, in Access 97. But when
I go thru the Updater . . .I get the error. Help me understand this please.
In addition, In Scenario #1, Even once Access 2003 is added to the mix
later, FE Updater seems to know which version of Access to open, even without
specifying a
startup in the ini file. This seems to be the case regardless of which
program I had open last, Access 97 or Access 2003. Since I may have a few
variations on where that exe is . . . . is this true??? Or will I possibly
develop problems.
Allot to digest, I know. But I have about 40 machines I need to think this
thru. The FE Update program has been marvelous in helping me bring Scenario 1
into full swing, with and subsequently getting Access 03 on the boxes.
You may be thinking, just convert en mass to Access 2003 and be done with
it. But I have specific reasons I need to be able to control FE conversions
sort of one DB at a time.
Thanks for taking the time to help me through this. I'm sure I need to
understand more about DAO in the midst of all this.
looking, finally , at the 2003 conversion of these databases. Setting the
actual conversion aside for now, I have an issue regarding the DAO when I use
a particular upgrade path. The situation below deals with the entire Office
97 and Office 03 install packages, but I am only focusing in on Access
On all boxes I am looking at (other than my test box, #3), it looks like
Access 97 was installed prior to 03.
Scenario #1 - On most machines, Office 97 was completely installed. Office
2003 was later installed, with the Option to NOT install Access 03 and to
leave Access 97. Default directories. On these machines, FEUpdater was added
and Access 97 FE/BE's via this tool have been operating just fine. You'd
expect this, because Access 03 was never installed in the first place. This
is where most machines are now. In addition, subsequently adding Access 2003
also seems to not harm the process.
Scenario #2 - There are also a few machines that were imaged slightly
different. On these machines, it *APPEARS* that with backward compatibility
in mind, these machines had Access 97 installed first, by itself (from the
Office 97 CD) and immediately had Office 2003 installed, complete - - - with
the option to KEEP Access 97 on the machine. But the directory location for
the 03 install was changed from the default Program Files\Office to Program
Files Office 2003
Again, these machines seem to operate fine in the FE/BE FEUpdater
environment opening Access 97 FEs.
Scenario #3 - But on a third variation test machine, I installed Office 2003
complete FIRST in it's default directory and then added Access 97 by itself
(with Spell Check). On this machine, when I try running the FEUpdater ini
for any 97 FE, I get a DAO error in the Auto FE Updater.
"The following error occurred while attempting to determine the Access/Jet
version of the file . . . . . (while using DAO Version 3.6). Error 3041:
Cannot open a database created with a previous version of your application."
I can manually open an Access FE without any problem, in Access 97. But when
I go thru the Updater . . .I get the error. Help me understand this please.
In addition, In Scenario #1, Even once Access 2003 is added to the mix
later, FE Updater seems to know which version of Access to open, even without
specifying a
startup in the ini file. This seems to be the case regardless of which
program I had open last, Access 97 or Access 2003. Since I may have a few
variations on where that exe is . . . . is this true??? Or will I possibly
develop problems.
Allot to digest, I know. But I have about 40 machines I need to think this
thru. The FE Update program has been marvelous in helping me bring Scenario 1
into full swing, with and subsequently getting Access 03 on the boxes.
You may be thinking, just convert en mass to Access 2003 and be done with
it. But I have specific reasons I need to be able to control FE conversions
sort of one DB at a time.
Thanks for taking the time to help me through this. I'm sure I need to
understand more about DAO in the midst of all this.