>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?

Unfortunately, no - if an ActiveX component already in memory is changed, all applications that hold connections to the component must be shut down before the changes to the ActiveX component are registered and available to create new instances of the object.