No installable ISAM

[Guest]

Hello,
I have been trying to solve a problem with ISAM errors. First I cannot
linked anything in Office Small Business (2003) or Access 2003 which did not
come with Office 03. I recently upgraded Access from 2002 to 2003. I do
believe that everything was working after the upgrade. Then last weekend
doing some routing maintenance, I removed the Office setup files, oops. This
is when I believe I started getting these ISAM errors. I cannot do a mail
merge in Word or Publisher. I also have an Access database that had a query
to create an Excel worksheet, not working also. I have located all of the
ISAM files listed at http://support.microsoft.com/default.aspx?id=283881 and
they are also in the registry. I have reinstalled Office and Access twice
with no luck. Any help would be appreciated. This is on a Dell laptop running
WinXP 2nd Edition.

Ron Brown

 

[Guest]

Just some thoughts,

1) Normally, the registry entries for Access point to some
kind of installation instruction or file protection list, not to
the executables.

But
2) AFFAIK the IISAM entries point directly to dll's not
to the installation instruction/ file protection list.

3) If you have installed all the service packs, the excel IISAM
msexcl40.dll has probably been replaced with MSAexp30.dll
If you previously applied the office service packs, you should
do so again.

(david)

 

[Guest]

David,
First of all thanks for replying!

#3 checked out, I am not sure what your #2 is telling me, can you elaborate?

 

[david epsom dot com dot au]

'Just thoughts'. If you look at the value for
hklm\access\application\11\shell\open\command\command
you will see what the registry entry for access looks
like (the \open\command default value is not normally
used). AFAIK, the IISAMS don't have anything like that,
so it has always been the case that if msexcl40.dll
had problems, it could just be replaced.

Which, by the way, is what you should do if you haven't
already. Unless there is something in the file protection
system which automatically overwrites your replacement
file...which we hope is not the case.

Sorry I can't help you with any good advice (~:

I guess if it was me, I'd be trying to make sure all the
files and registry entries where deleted before trying
to install again.

(david)