Access 97 problem

[Amiit Mangla]

Hi,

I had recently install office 97 on windows xp sp2. All is working fine but
when I am trying to open Access 97 it says
" The Dynamic link library MS09.DLL could not be located"
Pls resolve.

Rgds
Amit

 

[Pat Hartman\(MVP\)]

If you have newer versions of Access installed, the best option is to
uninstall all versions. Then reinstall them in chronological order with the
oldest first.

 

[Tony Toews]

Then reinstall them in chronological order with the
oldest first.

I have installed Access versions out of chronological order at least
six times in the last three or four years. I've never yet had any
problems other than the infamous A97 licensing error.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Pat Hartman\(MVP\)]

You must live right. Or maybe it's that Artic air I have had no luck
installing them out of order.

 

[Tom Wickerath]

I've run into one additional problem that Tony did not mention, which is
having the linked table wizard not display any linked tables. However, this
problem was easily corrected: http://support.microsoft.com/?id=835519

In my case, it was not possible to install in chronological order.
Approximately 8(?) months ago, we received brand new PC's at work with the
standard "Blockpoint 3.1" load, which included Windows XP Pro. and Office
2003. Access 97 was not included in Blockpoint 3.1 for anyone. If you needed
it to support your job, you needed to install it after the fact.

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

I just did a re-install: A2000 then A2003, which because it was a re-install
probably counts as installation in the wrong order.

A2003 deleted MSO9.dll every time it ran. Obviously some kind of 'file
protection' error. There was some kind of cross over of the Office paths,
even tho the two copies were installed to different folders

I've also had a complete installation failure for Access runtime, where the
mass-market PC with Windows pre-installed came with a pre-installed error in
the Windows system path, causing the Access installation to create a new
WinNT/System32 folder instead of using the Windows/System32 folder. When
tested, the WinAPI call was clearly returning the wrong value.

(david)