Hi David,

>Why should a new version matter is the public interface interface of an ocx is compatible???

Because we are talking about Microsoft. *g*

VFP stores some version info of the OLE control inside the OLE and OLE2 fields whenever you open and close a form. Whenever it instanciates the control it tries to find this or a new control, but won't recognize older ones. The easiest solution would be to give your client the same version as you have (as long it's no beta, that shouldn't be a problem).

Otherwise you have to remove the control from your form, install the old component and add the control again. I think Ken Levy had some tool that could help here (www.classx.com). Doug Hennig had an article about this some time ago in FoxTalk. The essence was that he now only adds a loader control the form and defines the ActiveX control in code, because then VFP can use the ProgID to find whatever control is installed on the system and doesn't use anything else.

Christof