Hi!

Its strange. In VFP you can use SQLSETPROP(0,'DispWarnings') before any connecting through ODBC, that will disable warning messages. With ADO, I guess, should be something like that too. Or just try to catch an error by wrapping the connection open into the ON ERROR... statements. I experiensed a lot of such weird things with ADO too, and sometimes in VB application I had to disable errors temporarily because no other way to check if something works or not.

HTH.

>I would appreciate any thoughts on the following: I'm using ADO to access a Foxpro database:
>WITH oConnection
> .OPEN("Driver={Microsoft Visual FoxPro Driver};UID=;SourceDB=C:\SS\VFP\Delivery Address Pool\Data\deldata.dbc;SourceType=DBC;Exclusive=No;BackgroundFetch=Yes;Collate=Machine;Null=Yes;Deleted=Yes;")
>ENDWITH
>When I interrogate the error collection of oConnection I get "[Microsoft][ODBC Driver Manager]Driver's SQLConnectAttr failed" with an error number of 0.
>However, if I let the program continue it opens a record set on this connection with no problems!