Terry,
Generally I wonder when it doesn't work :)
It's expected to work. Because you simply add a new property and assign an object ref in one step :)
Cetin

>I did something I didn't think should work. But it does. I created an ADODC com (EXE) and an ADODB comm (DLL).
>What do yo think:
>
>define class ado as custom olepublic
>oConnection=CreateObject("adodb.connection")
>enddef
>
>This worked! I was able to build a DLL. Of course I packed it with procedures and other ADODB objects. I thought there was some supposed issue with CreateObject inside a subclass - but this works - AND I wonder why?
>I will check the thread you forwarded.
>
>>>Cetin,
>>> I know this is an old thread, but I'm trying to figure out how to instanciate the ADODC (not ADODB) in code. The (visual) ADODC com works with the simple stuff being put through it. When attempting to instanciate in code, ODBC errors popup with Provider errors (Error 0?). Note: the ADODC property pane does not offer "Provider" and that the ADO.Refresh call pops these errors. Got any thing to share or shed about ADODC? Is it different from ADODB, or is that a subclass name? :) PS: CommandType is 8 (unknown) and the RecordSource calls a NortWind stored procedure.
>>>
>>>>oRecordset = CreateObject("adodb.recordset")
>>>>oConnection = CreateObject("adodb.connection")
>>
>>Terry,
>>I'm not sure what you ask is this but check Thread #328681
>>Cetin