On Wed, 10 Oct 2001, Michael Davis wrote:
> Edit the ODBC driver DSN that you are using to connect to PostgreSQL and
> turn on or enable the "CommLog" option. It can be found by clicking on the
> "Driver" button. Try your search in Access again. This should create a
> file in the C: drive of the PC you are running Access on called
> c:\psqlodbc????.log where ???? is a number. If there are many of these
> types of files in your C: drive, the select the latest file and review it's
> contents. This should show everything that happens between Access and
> PostgreSQL. This log file has helped me resolve 90% of my issues with
> Access. If it is still unclear what the problem is, then please email the
> log file.
Thank's in advance to spend your time :). But I've never enabled CommLog
(I thing that postmaster and tcpdump will give more information).
I've diving in microsoft.com, and I've instaled the last Jet engine, but
the problem persists. I've also chage some parametres in regedit.exe.
I'll gave you information when I'll know something else. Thank everybody
:)
_____ - - - - - - - - - Alejandro Alfonso Fernández - - - - - - - - -
/\___/\ Grupo Universitario de Informática - Diplomatura en Estadística
/__\ _\/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
/_/\_\ - "Lo mejor de tu ordenador está entre tu silla y tu teclado" -
/_/ /\_\ Atari Php Asp Wap Sql Dhtml Swf JavaScript Java Xml C Awk Sed
\_\/ \_\ - Email: kawa@gui.uva.es - Web: http://www.gui.uva.es/~kawa/ -
L.Carrol: Hace falta que corras todo lo que puedas para seguir en el mismo
sitio. Si quieres ir a alguna parte, tendras que correr el doble de rapido!
*gpg*public*key->http://www.gui.uva.es/%7ekawa/alexokawa.gpg<-gpg*public*key