>>Dave,
>>
>>THanks.. I'm just a little concerned - along the lines of what Dragan is discussing. IOW, I don't want to inadvertantly send out new DLLS or whatever that might get compiled into what should be a 100% 6.0 build.
>>
>
>DLLs and OCXs don't ever get compiled into an exe. ActiveX controls that are dropped onto forms, however, do put a cause a version specific ProgID to be stored in the SCX, so if you drop a newer version of an ActiveX control onto a form, and compile and distribute that exe to a machine that does not have that version installed, it will crash.

Frankly, I was more concerned with the behind-the-scenes stuff, i.e. the things which got installed before the VS.NET (upgrading IE to 5.5 and who knows what else). Though these things are not part of our forms (and I am relieved that the versions of OCXes are distinguished now - remember the 5.0/6.0 treeview and imagelist nightmare), but some other dlls may be part of an install. Well, it's long since I ever was involved in building an install, and one fears the things he doesn't know well, right?