This connection string works for me:
csp = "ODBC;DRIVER={PostgreSQL};UID=" & unm & ";PWD=" & pd &
";DATABASE=pbend;SERVER=" & DBSrvr &
";PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIO
NING=1;SHOWSYSTEMTABLES=0;CONNSETTINGS="
where the backend is called pbend, DBSrvr holds the server ip, unm holds the
username and pd holds the password. I've included row versioning which may
be what is making the difference.
I then establish a connection to the back end in the following manner
Set pg_bend = DBEngine.Workspaces(0).OpenDatabase("", False,
dbDriverNoPrompt, csp)
pg_bend.Close
This seems to work for me with Access 97, Pg7.1B4, and psqlodbc 7.01.0003.
(Latest version should be available at:
http://www.greatbridge.org/project/pgadmin/download/download.php)
One thing that might help is to make sure access has some unique way of
iding the record.
> -----Original Message-----
> From: Schollum(at)t-online(dot)de [SMTP:Schollum(at)t-online(dot)de]
> Sent: Friday, March 16, 2001 9:57 PM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: Re: Problems with Acess
>
> 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
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.237 / Virus Database: 115 - Release Date: 07/03/01
>
> << File: psqlodbc_168.log >>