>>the OCXs each have a version number associated with them. You can retrieve
>>this by using GetFileVersion() with foxtools in 5.0, or AGETFILEVERSION() in
>>6.0. In both cases, the version number will be stored in the 4th array
>>element. In 5.0 dimension to array to at least 12 elements. In 6.0, 15
>>elements are returned.
>
>True, but I want to also check to see if the controls are registered. As you know, sometimes the file is there but it wasn't registered properly because of some crazy dll conflict or some $$%%*&&@! thing.
>
>tia
>
Hi scott,

Well, you can check the registry for the fully file name in the HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\< file name > key. Of course, this only applies to those controls from MS. Finding the license (CLSID) would be very time consuming, since you'd have to enumerate every license under the HKEY_CLASSES_ROOT\CLSID node looking for the fully qualified file name. Even that won't do the trick 100% of the time. It's perfectly possible (and I've experienced this) to have a registry entry for the control, and have it been incorrect. About the only thing I can recommend, would be to track the current installed ActiveX controls and their versions in a table. When a new one was to be installed, I'd suggest a special setup to do it, created with the setup wizard. You could check the versions, and run the new setup routine if a newer version was available. The only other possibility would be to run regsvr32 in silent mode (with the /s switch).