Basically, if the ActiveX is already in use, you cannot register a new version of that ActiveX. If the ActiveX is not in use, you can register it and use it right away.

One more thing: the dedicated directory for ActiveX/OCX controls is the System directory (usually C:\Windows\System) and not the root. You can use the GetSystemDirectory() Win32 API function to retrieve the system directory.

Vlad

>When adding certain APP's to an existing VFP 5.0a run time, we are occasionally forced to update an ActiveX component -- since it is either totally missing or out-of-date. We have added the coding to dynamically copy the component to the 'boot directory' and 'register' it using code as posted on the Universal Thread website by Paul Vlad Tatavu. We then display a message that in order to use the feature, the user needs to exit from the program and re-run it -- not restart their whole system. Is there a method to immediately activate a changed ActiveX component?