>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 :)
Yes, but I never considered CREATEOBJ as adding to the super-class (Maybe that was a form container). I expected to need an AddObject or ADD OBJECT. What is new to me is that the CREATEOBJ is treated like a child of the Super, with some referencing exceptions inside a Super procedure.

>>define class ado as custom olepublic
>>oConnection=CreateObject("adodb.connection")
>>enddef

I also noticed that I could not reference inside a com procedure as: THIS.oConnection
Before the procedure declaration the COM needed to see: oCon=this.oConnection. (wierd)
About ADODB.Error: Is their a way to trap or reset an Error before the Open method crashes due to quel syntax. With the ADODC (exe) com, there is a 'contained' error method, where I could set some com status flags and return a status string (as well as) a .NULL. Record set.

I'm trying to figure out how to reset (close) the RecordSet Open before it yields to a SQL Error or Provider Error.
Any ideas?