Type mismatch only on some machines.

Dear friends,

I am getting a "Type mismatch error 13" AFTER running my Installshield setup. The error had been only occurring on Windows 95/98 machines. I did some tinkering (total trial and error) and now it works with my 98 machine and one of my XP machines, but not on my XP laptop!?!

The error only occurs on some machines which must mean it is not a programming error (as I know the type mismatch usually is). I believe (as did my installshield support rep) that this is being caused by a missing or corrupt .dll or .ocx file.

I have scanned and scanned for dependencies and included all the Installshield and PDW recommended ones. I recently also ran the PDW and made sure all the files in its list were included in the install.

The PDW list was:

comdlg32.ocx
dao350.dll
expsrv.dll
msjet35.dll
msjint35.dll
msjter35.dll
msrd2x35.dll
msrepl35.dll
msvcrt40.dll
noteable.exe (my compiled program)
richtx32.ocx
scc_11.ocx (a third party sound card control)
scrrun.dll
vb5db.dll
vb6 runtime and OLE automation

I have checked that the laptop has all these files after the install and it does. I also manually registered all these to make sure they had been successfully registered using the "regsvr32 [filepath]" command.

The error occurs AFTER installation right after the program begins to run. What perplexes me is that the software works fine on two of my machines, but gives the error on the third. Plus the software works on one of my XP machines but not on the other XP machine!

Could anybody help? Also a brief explanation of what the heck these .dlls do might be nice.

Thank you!
-Mark

After relaxing for a bit, and searching some more, the answer came.

I have three test machines: A laptop running Windows XP, a desktop running Windows XP, and a Desktop running Windows 98.

The problem was that the laptop had some older program files (made by my software) that were not compatible with the newer version. So, when the file was loaded I got a type mismatch because the values did not match. The error was not from a missing .dll! Sure enough, it was my fault after all (course the uninstall SHOULD clean everything off. sheesh).

Unbelievable how I could struggle with this for days, make a post, and then almost immediately discover the answer. That's the way life works I s'pose.

Sorry 'bout the trouble folks.

I still wonder what those .dlls do if anyone knows.

-Mark