the registering key supposed to be used for developers only to develop applications. Why you want it is available for development at the client machine?

Anyway, I do not know a way to avoid the replacement of the ActiveX control. You can, of course, create a class and add that control on the fly to the form in run-time. While your customer will be able to edit a form (without ActiveX placed on it), he will not be able to edit that ActiveX control class.

HTH.

>Vlad:
>
>>>You will not be able to modify forms with that ActiveX control if registering number is different. Forms will still run in the compiled EXE correctly, just because they use only GUID number of the ActiveX control to run it, that is similar for a specific ActiveX at all computers.
>
>Yeah, I know that, but is there any way to get around this? The only thing I can think of is to remove the controls off the forms then move the application to the new machine, then put them back. Sounds like a lot of work.
>
>Charlie