ADO's biggest weakness is it's erroneous error reporting (2nd would be the errors rampant throughout the documentation!). But it works great once you know where the landmines are!

I remember going through those pains in VFP as well (remember filtered recordsets and the NOFILTER clause!)

Glad to help,
Ed


>Ed, that worked! Interesting thing is that the INSERT INTO I used dbl quotes and it worked... Nothing like a double standard. :) Thank you very much.
>
>
>>I believe ADO uses single quotes Chr(39) instead of Chr(34). Give it a try.
>>
>>>Does anyone see a major prob with the following: It doesn't like the commandtext line...
>>>
>>>

>>>Dim cn As New ADODB.Connection
>>>Dim cm As New ADODB.Command
>>>cn.Open "Driver=Microsoft Visual Foxpro Driver;UID=;SourceType=DBF;Deleted=YES;Null=NO;SourceDB=D:\"
>>>cm.ActiveConnection = cn
>>>cm.CommandType = adCmdUnknown
>>>cm.CommandText = "DELETE FROM C:\windows\system\Q12.dbf WHERE officeno = " & Chr(34) & cboOfficeNum.List(cboOfficeNum.ListIndex) & Chr(34)
>>>cm2.Execute
>>>

>>>My AdvaThanksnce