>Hi Tom.
>The only machine that runs the new EXE and SP6 DLLS is the machine that 'installed' the service pack.
>When our new exe and dlls are moved to any other machine that ran the SP5 version of our EXE, the message comes up when we try to launch.
>So, that it why I think there is an operating system file that is being updated by the SP6 install; we would need to include that OS file with any updates sent to our customers. (>It sounds like you have missing or obsolete file(s). -> I agree, and I'd like to know which DLL/OCX/etc really needs to be distributed.)
>
GorgAnna;

Somewhere in my collection I have this really neat exe - it has two windows - the upper window shows what dll's, etc. are being called by a calling exe, and the lower window shows what dll's, etc. are actually being used. It also gives dates and versions of the dll's, etc. This has been a life saver for my Visual Basic installations - and I think you could use such a utility. I will try to find it but I am not going to promise success. I remember I was on the UT VB forum about two years ago when I posted a similar problem and a kind developer sent me the exe. Maybe you could try the VB guys - they always have problems like this - after all, VB is full of dll's. I had one app with about 100 of them - the fun of it all!

Hope you resolve this quickly.

Tom