Unless you use A LOT of ActiveX controls, the performance hit will be null/zero/nada. :) A search for a clsid in the registry is very fast, don't worry about it. And this search is done anyway when an ActiveX is instantiated.

Vlad

> Because it is not always necessary to do this check--only when a form fails to instantiate. My design philosophy here is: why make the user take a performance hit when it's not necessary? Most of the time, it will not be necessary. The hit should be necessary only once per machine, the first time the user tries to run a form that requires an activeX control. By testing for missing ocx's only when necessary, the design saves the user a great deal of time over the long run.
> Also, I want the system startup to be as fast as possible.
> Regards, Chaim