James,

I added my business object classes, set one of my business objects to OLE Public and instantiated it. It worked!!! Now let me try an Event.

TIA

Rex

BTW, according to the manual, you should instantiate the CApplicationCOM object if you are instantiating multiple objects so they can take advantage of the several managers created within the application object. I'd like to get this to work.



>>James,
>>
>>I am in Win 95/98.
>>
>>Here's the latest:
>>
>>I have recreated my ImpactCOM project.
>>
>>First I created a DLL from just the MM base class libraries and programs. I created a CAbstractFactory class successfully.
>>
>>Next I created ImpactCOMObject as a subclass of CApplicationCOM. I set ImpactCOMObject OLEPublic to .T.. When I try to create an ImpactCOMObject instance, I get an:
>>
>> OLE Error code 0x80004005 Unspecified error
>>
>
>Rex, instead of creating your application object, try marking your event object as ole public and creating that instead. Example: oTest= createobj("ImpactCOM.myEvent") Make sure the autorun property is set to false, and then run it manually. The application object is not meant to be created directly. It is used by your bizobjs for support methods and procedures. Another test would be to mark one of your bizobjs as ole public and creating that. You can have more than one object marked as ole public. The ones that are not marked as ole public can still be called from within the com object, but they will not have a public interface.