AW: Re: Problems with Acess

Look at this page for the newest odbc
http://www.greatbridge.org/project/pgadmin/projdisplay.php

M.Moehle

MBD-Team Bordesholm
Bahnhofstrasse 41
24582 Bordesholm
m(dot)moehle(at)nikocity(dot)de

-----Ursprungliche Nachricht-----
Von: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org]Im Auftrag von Michael Davis
Gesendet: Freitag, 16. Marz 2001 22:35
An: 'boopet(at)web(dot)de'; pgsql-odbc(at)postgresql(dot)org
Betreff: RE: [ODBC] Re: Problems with Acess

I am not sure what is causing this. I wonder if there is a more recent
version of the ODBC driver that addresses this issue? I believe that one
of the later versions of PostgreSQL (maybe 7.1) did not play well with the
existing ODBC driver. When I downloaded and installed the newer ODBS
driver thinks worked better. You will have to research the archives for
the email that talks about where to download the latest version of the ODBC
driver because I did not save it.

-----Original Message-----
From: Norbert Schollum [SMTP:Schollum(at)t-online(dot)de]
Sent: Friday, March 16, 2001 2:57 PM
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Re: Problems with Acess

<< File: psqlodbc_168.log >> << File: ATT00001.txt >> i cant find any hint
in this file.
the transaction is stopped by Rollback.

it would be interesting, what Postgres is telling Access ....

i have attached the logfile.

Michael Davis wrote:
>
> Turn on logging in the PostgreSQL ODBC driver, retry the update, and look
> at c:\psqlodbc###.log. This log file has been very helpful at helping
see
> what Access is telling PostgreSQL to do.
>
> -----Original Message-----
> From: Norbert Schollum [SMTP:Schollum(at)t-online(dot)de]
> Sent: Friday, March 16, 2001 2:32 PM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] Re: Problems with Acess
>
> i cant update the record even if i quit access and restart it.
> what else could be wrong?
>
> Fabio Nanni wrote:
> >
> > Hi,
> > I experienced the same type of problem in the past, but not now. I
> > cannot say why, too many things are changed in the meantime
> > (PostgreSQL7.1B4, W$2K, Access2K, odbc 7.X), but perhaps you can try to
> > refresh the record you just modified before trying a second update (or
> > modify the refresh interval of the linked tables, in
> > Tools->Options->Advanced->ODBC refresh interval).
> >
> > hope this helps...
> > Fabio
> >
> > Norbert Schollum wrote:
> > >
> > > Hello,
> > >
> > > ...
> > > but there are some entries, which i can only edit one time.
> > > the next time i try to update them, i get the message,
> > > that another user is working on this entry - but there is
> > > no other user doing this!
>
> --
> Comtec Computersysteme
> Norbert Schollum -=-_-- ICQ 4261631
> Lindenweg 9 Fon+Fax (0700) 333 888 00
> 84576 Teising http://www.comtec-computer.de
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

--
Comtec Computersysteme
Norbert Schollum -=-_-- ICQ 4261631
Lindenweg 9 Fon+Fax (0700) 333 888 00
84576 Teising http://www.comtec-computer.de

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly