>Using Visual Foxpro 5.0 we are creating an Active X DLL created in visual Basic 6.0 using the CreateObject function. After running some tests we have determined that the ClsID is not compiling into the executable, which means that IDispatch is being used via COM and thus the calls to the Active X dll are late bound. Is this a function of the CreateObject function? Does the VFP 5.0 compiler not have the capacity to do early binding with COM objects? Is there anyway we can accomplish earlybinding using a different technique than CreateObject?


VFP5 and 6 are only capable of late binding. Early binding has been added to VFP7.