>In Delphi in the Implementation Unit of the ActiveX control in the Initialization of the control it calls the following:
>
>TActiveFormFactory.Create(
> ComServer,
> TActiveFormControl,
> TMEIScheduleControl,
> Class_MEIScheduleControl,
> 1,
> '{1D3E976A-B76C-4D1C-B7BD-ACEF6AF04B95}',
> OLEMISC_SIMPLEFRAME or OLEMISC_ACTSLIKELABEL,
> tmApartment);
>
>I took out the OLEMISC_SIMPLEFRAME support which isn't needed by VFP or VB anymore and VOILA!
>
>
>Really COOL!
>
>George, now if you knew how to link to the VFP OCXAPI.LIB from Delphi and we are really cooking! I haven't found enough documentation yet to show me how to properly link to the LIB file from Delphi. But when I do!!

Rich,

I'm not 100% sure of this, but according to the Platform SDK, AfxOleRegisterControlClass() creates registry entries that appear to include this information. I have, however, apparently be unable to trackdown exactly where. I did find information under the CLSID of the Toolbar 6.0 ActiveX control that appeared to be a string containing this information (MiscStatus\1 key). The string which stored a numeric value that evaluated to OLEMISC_ALIGNABLE, OLEMISC_ACTSLIKELABEL, OLEMISC_SIMPLEFRAME, OLEMISC_SETCLIENTSITEFIRST and some additional value. I modified this to make it reflect the value without OLEMISC_SIMPLEFRAME, but without success.

One thing that occurred was, what happens if you install an SP? Would the changed be reversed?