William - I'm sorry I didn't get right back to you. It's been a while since this happened that I don't remember which dlls weren't unregistering. I have since talked to a consultant at InstallShield who mentioned that 3.5 wasn't completely compatable with XP. I don't know if that might be part of your problem but you can test it out by downloading a trial version of Express 4.0 from the InstallShield web site. It didn't solve all my problems but most of the dlls that weren't unregistering did unregister with 4.0.

It would be nice to know exactly which dll's and ocx's absolutely have to be registered and which ones you can get by with by just putting them in the application, and which ones you can get by with by just putting them in the system folder, without registering them.

I hope this is of some help. - Mike

>I was wondering which DLL's weren't properly unregistered to know how InstallShield fails... for my own projects, too: Does it properly unregister COM objects that it registered? and the VFP Runtime DLLs?
>
>>Thanks for responding William -
>>
>>Norton SystemWorks WinDoctor provided the id for each registry entry so I was able to use regedit to search for the entries. The name of each of the dll's that were giving me problems were in the registry entries. It didn't solve all my problems but it was nice to have the universe narrowed to a few dlls.
>>
>>Thanks!