Erik - couple questions
1 - is th GUID the very long hex-looking number in the registry under CLSID?
2 - where is this stored in class (form) definition (VCX) - is it encoded in the OLE field? because the only thing I see is a path to the actual OCX file in Windows\System
3 - not sure what you mean by "scroll down to that name to find its other entry" - in this case Calendar Control 8.0 - not sure where you mean to go to
thanks!
Ken
>Use Regedit and navigate to HKEY_CLASSES_ROOT\CLSID. Listed there are all the GUIDs associated with your ActiveX and COM objects. Look in the desciption of each field to get its name, and scroll down to that name to find its other entry.
>
>When you drop an ACtiveX control onto a form, it's GUID is stored in the form definition, and when the form is opened or run, the related ocx file is looked up directly from that GUID. But when you instanciate an ActiveX control or COM object with CREATEOBJECT('MyServer.MyClass') the system looks up MyServer.MyClass in HKEY_CLASSES_ROOT, finds it's GUID from there, looks up the GUID in HKEY_CLASSES_ROOT\CLSID, and finds the file from that entry.
>
>This is why it can be advantageous to instanciate the controls in code, because versioning is less of an issue: the GUID is looked up dynamically from the control name.
Ken B. Matson
GCom2 Solutions