I developed an Excel application where the worksheets reference DLLs that I
wrote. It is several versions old, and all DLLs are compiled with binary
compatibility to the previous version. All DLLs have always worked on all
user machines.

Now, they still work on mine, but on user machines after the install of the
new version, the references dialog indicates that the DLL is missing. When
that is unchecked, closed, reopened, the DLL found & checked, the path is
lower case. When the file is saved, closed & reopened, the DLL shows again as
missing.

Just before this version was installed, all machines were upgraded to Office
2003 sp2 and to XP sp2. There's probably a catch here somewhere.

Any ideas?
Thanks in advance - Stoney

after the install of the new version

Does that include registration (regsvr32) ..

Regards,
Peter T

"Stoney" wrote in message
...
I developed an Excel application where the worksheets reference DLLs that
I
wrote. It is several versions old, and all DLLs are compiled with binary
compatibility to the previous version. All DLLs have always worked on all
user machines.

Now, they still work on mine, but on user machines after the install of
the
new version, the references dialog indicates that the DLL is missing. When
that is unchecked, closed, reopened, the DLL found & checked, the path is
lower case. When the file is saved, closed & reopened, the DLL shows again
as
missing.

Just before this version was installed, all machines were upgraded to
Office
2003 sp2 and to XP sp2. There's probably a catch here somewhere.

Any ideas?
Thanks in advance - Stoney

Absolutely. with first an Un-regsvr32, then a regsvr32.
Stoney

"Peter T" wrote:

after the install of the new version

Does that include registration (regsvr32) ..

Regards,
Peter T

"Stoney" wrote in message
...
I developed an Excel application where the worksheets reference DLLs that
I
wrote. It is several versions old, and all DLLs are compiled with binary
compatibility to the previous version. All DLLs have always worked on all
user machines.

Now, they still work on mine, but on user machines after the install of
the
new version, the references dialog indicates that the DLL is missing. When
that is unchecked, closed, reopened, the DLL found & checked, the path is
lower case. When the file is saved, closed & reopened, the DLL shows again
as
missing.

Just before this version was installed, all machines were upgraded to
Office
2003 sp2 and to XP sp2. There's probably a catch here somewhere.

Any ideas?
Thanks in advance - Stoney

I don't know! also not sure if change of case is directly relevant.

Absolutely sure compatibility was never broken ?
Does the dll have any references to Office App's, eg Excel, if so was the
dll compiled with these set to the oldest *.olb that any user might have.

The Windows & Office upgrade, anything different about relative path's
particularly as regards multiple users if different from the previous setup.

Guess none of the above not related, maybe doing the following might lead
somewhere -

Temporarily register the old dll on your machine (same version that
previously worked on user's system). Make an xls (file1) with a ref set to
the old dll. Include some code to test all the exposed methods in the old
dll.

copy file1 to file2
Re-register the new dll
remove the ref in file2 and set a ref to the new dll.
Check file1 & file2 both work on your machine with file1 now using the new
dll (but don't save file1 with the new dll registered)

Send both files to your users to test with the new dll registered on their
machine.

Regards,
Peter T


"Stoney" wrote in message
...
Absolutely. with first an Un-regsvr32, then a regsvr32.
Stoney

"Peter T" wrote:

after the install of the new version

Does that include registration (regsvr32) ..

Regards,
Peter T

"Stoney" wrote in message
...
I developed an Excel application where the worksheets reference DLLs
that
I
wrote. It is several versions old, and all DLLs are compiled with
binary
compatibility to the previous version. All DLLs have always worked on
all
user machines.

Now, they still work on mine, but on user machines after the install
of
the
new version, the references dialog indicates that the DLL is missing.
When
that is unchecked, closed, reopened, the DLL found & checked, the path
is
lower case. When the file is saved, closed & reopened, the DLL shows
again
as
missing.

Just before this version was installed, all machines were upgraded to
Office
2003 sp2 and to XP sp2. There's probably a catch here somewhere.

Any ideas?
Thanks in advance - Stoney