How to launch Access 97 from Word 2000

[bof]

I have a WinXP machine that has had Office 2000 installed, in order to
mailmerge Word documents and work with an existing Access 97 database
Access 97 was been subsequently installed.


I can double-click launch the database into Access 97 having changed
Explorers "Tools > Folder Options > File types" to link to Access 97,
which initially launched Access 2000.


However, when running the mailmerge process which is launched from
Access 97, Word 2000 launches Access 2000 to attempt to access the
database, so, ... how can I change this so that Word 2000 launches
Access 97, not Access 2000?

Any advice? MTIA


(The longterm fix will be to convert the database to Access 2000, but
this is throwing up a lot of problems so as a temporary fix I'd like to
get Word 2000 launching the post installed Access 97.)

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[DL]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.
You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[bof]

"Access 97 was been subsequently installed"
If you installed A97 after Office2k, that includes A2k, you may well have
compromised your entire installation.
You should install the earliest version first, update, then install the
later version. In these two instances using Custom installation to install
to a version specific folder. - Later versions install to a version specific
folder.

Well, that's along the lines of what I'd have done, but in this case I'm
working with a corporate installed machine, within the constraints of an
inflexible IT policy.

You would also need to amend shortcuts after the first installation, to be
version specific ie Access97 as apposed to Access.
I would reccomend you start anew.

You should be able to select the correct data source within word, I believe
you will have to alter the file associations so that access files are opened
with A97, and not the default A2k

Yep, this is what I'm trying to achieve, but how do I change the
associations in Word2k to point to A97. The help in Word2k only says to
change the association in Windows Explorer, which doesn't change the
association in Word2k.

PS Its not to much of a problem converting a db to A2k, generally you may
only find problems with a few lines of code, it really depends on to what
extent the db is coded. It didnt take me long the last time I did this.

Unfortunately this is a very heavily coded database that links to and
from Outlook, Word and Excel sources so there's quite a bit of work
needs doing for the full conversion.

 

[DL]

Maybe some of this will help; its from a file I found when I was running two
versions of Access

PS I'm not entirely sure that Word2k can be forced to use A97 if A2k is
installed, even if file associations are changed.

Installing Office versions out of sequence, particularly to a none version
specific folder, will allmost certainly cause problems. These are MS
instructions / advice, perhaps your IT dept should be aquinted of this.

---------------------


When installing / using multiple versions of MS suites or
applications:

1. Install the oldest version first
2. Install in a separate folder, directory or partition.
3. If you want to keep your start menu shortcuts then rename them
before installing a newer version.
4. Do a custom install and do not overwrite/replace the older
versions. However...
5. Only one version of Outlook can be installed on a single operating
system.
6. You should specify the default version of each application by
registering it using 'Start | Run'. If you don't register the
application then the last version installed becomes the default.

(Enter the full file path and name of the program, note that
/regserver is outside the quote marks.)
"C:\Program Files\Microsoft Office\Office\Excel.exe" /regserver
The above will register Excel 97 as the default on most systems -
change the file path / file name as appropriate.


< NB you will have to edit above to ensure it points to your A97




7. Do Not run multiple application versions at the same time.
Close one before opening the other.
8. MS knowledge base articles follow in no particular order:
292491 -
Office Automation When Multiple Versions of Office AreInstalled
290576 -
OffXP: Running Multiple Versions of Microsoft Office
218861 -
Off2000: Running Multiple Versions of Microsoft Office
214388 -
XL2000: Running Multiple Versions of Microsoft Excel
292584 -
OffXP: Setup Overwrites Start Menu Items from Earlier Versions of office
210391 -
Off2000: Setup May Remove Older Components

(Just in case)
233499 -
Off2000: How To Change the Company Name and User Name After Setup
290528 -
HowTo: Change the Company Name and User Name in an Office XP Program

 

[DL]

Maybe some of this will help; its from a file I found when I was running two
versions of Access

PS I'm not entirely sure that Word2k can be forced to use A97 if A2k is
installed, even if file associations are changed.

Installing Office versions out of sequence, particularly to a none version
specific folder, will allmost certainly cause problems. These are MS
instructions / advice, perhaps your IT dept should be aquinted of this.

---------------------


When installing / using multiple versions of MS suites or
applications:

1. Install the oldest version first
2. Install in a separate folder, directory or partition.
3. If you want to keep your start menu shortcuts then rename them
before installing a newer version.
4. Do a custom install and do not overwrite/replace the older
versions. However...
5. Only one version of Outlook can be installed on a single operating
system.
6. You should specify the default version of each application by
registering it using 'Start | Run'. If you don't register the
application then the last version installed becomes the default.

(Enter the full file path and name of the program, note that
/regserver is outside the quote marks.)
"C:\Program Files\Microsoft Office\Office\Excel.exe" /regserver
The above will register Excel 97 as the default on most systems -
change the file path / file name as appropriate.


< NB you will have to edit above to ensure it points to your A97




7. Do Not run multiple application versions at the same time.
Close one before opening the other.
8. MS knowledge base articles follow in no particular order:
292491 -
Office Automation When Multiple Versions of Office AreInstalled
290576 -
OffXP: Running Multiple Versions of Microsoft Office
218861 -
Off2000: Running Multiple Versions of Microsoft Office
214388 -
XL2000: Running Multiple Versions of Microsoft Excel
292584 -
OffXP: Setup Overwrites Start Menu Items from Earlier Versions of office
210391 -
Off2000: Setup May Remove Older Components

(Just in case)
233499 -
Off2000: How To Change the Company Name and User Name After Setup
290528 -
HowTo: Change the Company Name and User Name in an Office XP Program

 

[DL]

Maybe some of this will help; its from a file I found when I was running two
versions of Access

PS I'm not entirely sure that Word2k can be forced to use A97 if A2k is
installed, even if file associations are changed.

Installing Office versions out of sequence, particularly to a none version
specific folder, will allmost certainly cause problems. These are MS
instructions / advice, perhaps your IT dept should be aquinted of this.

---------------------


When installing / using multiple versions of MS suites or
applications:

1. Install the oldest version first
2. Install in a separate folder, directory or partition.
3. If you want to keep your start menu shortcuts then rename them
before installing a newer version.
4. Do a custom install and do not overwrite/replace the older
versions. However...
5. Only one version of Outlook can be installed on a single operating
system.
6. You should specify the default version of each application by
registering it using 'Start | Run'. If you don't register the
application then the last version installed becomes the default.

(Enter the full file path and name of the program, note that
/regserver is outside the quote marks.)
"C:\Program Files\Microsoft Office\Office\Excel.exe" /regserver
The above will register Excel 97 as the default on most systems -
change the file path / file name as appropriate.


< NB you will have to edit above to ensure it points to your A97




7. Do Not run multiple application versions at the same time.
Close one before opening the other.
8. MS knowledge base articles follow in no particular order:
292491 -
Office Automation When Multiple Versions of Office AreInstalled
290576 -
OffXP: Running Multiple Versions of Microsoft Office
218861 -
Off2000: Running Multiple Versions of Microsoft Office
214388 -
XL2000: Running Multiple Versions of Microsoft Excel
292584 -
OffXP: Setup Overwrites Start Menu Items from Earlier Versions of office
210391 -
Off2000: Setup May Remove Older Components

(Just in case)
233499 -
Off2000: How To Change the Company Name and User Name After Setup
290528 -
HowTo: Change the Company Name and User Name in an Office XP Program