Hello,
What I'm interested in, is the actual data that is returned by the server, and
as you mention, it is not traced by this tool.
I'm opening Access forms with a filter, and I'd like to know where the
filtering is actually taking place: on the server, or on the client? I have a
low-bandwith connection between the client and the server, this is something I
have to take care of.
Thanks
Philippe
-----Message d'origine-----
De : Benjamin Riefenstahl [mailto:Benjamin.Riefenstahl@xxxxxxxx]
Envoyé : mardi, 9. décembre 2003 18:42
À : Philippe Lang
Cc : Pgsql-Odbc (E-Mail)
Objet : Re: [ODBC] Sniffer to trace ODBC calls?
Hi Philippe,
"Philippe Lang" <philippe.lang@xxxxxxxxxxxxxx> writes:
> Is there, for Windows or Unix, an ODBC "sniffer", that would allow
> to look at the queries and results that got through a network?
> Something like tcpdump or ethereal, but that shows ODBC calls and
> results more clearly.
Windows: See the "Tracing" tab in the "ODBC Data Source
Administrator". I think the trace only logs the queries and error
codes, not the actual data, but that should be enough usually.
benny
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|