Yes there is. In ODBC in Control Panel, there is Tracing tab. Set the file
name and click "Start Tracing Now". In the resultant file, search for
"Select", "Update", "Insert" to find your SQL statements.
> boolean values translated as "Verdadero"/"Falso" on spanish (for
> True/False
> values), and I bet this is the reason. If I could log the calls to a file,
There are also Date/Time formats, MM/DD/YYYY vs. DD/MM/YYYY. Today is the
13th and cannot be a month.
> Is there a way to log to file the SQL statements on ADO
> Recordset.Open/Connection.Execute calls?
[quoted text clipped - 16 lines]
>
> JP
Joao Paulo Faria - 13 Oct 2005 20:31 GMT
Hum, I'm using ADO+ Jet not ADO + ODBC. It doesn't seem to work on Jet.
By the way, I said localized versions of Jet translatge some crucial words
like TRUE/FALSE, and it's the VB runtime, not Jet.
I'm aware about date formats. Thanks anyway.
"Someone" <nobody@cox.net>
> Yes there is. In ODBC in Control Panel, there is Tracing tab. Set the file
> name and click "Start Tracing Now". In the resultant file, search for
[quoted text clipped - 28 lines]
> >
> > JP
William (Bill) Vaughn - 28 Oct 2005 20:14 GMT
Yes, in ADO.NET 2.0 you can enable TRACE for all providers.

Signature
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
www.sqlreportingservices.net
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
> Hum, I'm using ADO+ Jet not ADO + ODBC. It doesn't seem to work on Jet.
>
[quoted text clipped - 44 lines]
>> >
>> > JP