Thread: Problems with Acess

Problems with Acess

From
Schollum@t-online.de (Norbert Schollum)
Date:
Hello,

i have updated a linked table on MS-access several times.
on some DB-entries this works fine many times.

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!
i can only cancel the transaction - no chance to do anything.

using psql updating works fine.
is there a known bug in the odbc driver?

please contact me at boopet@web.de if you can help me!

thanks a lot!
norbert


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

Re: Problems with Acess

From
Fabio Nanni
Date:
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!

Re: Problems with Acess

From
Schollum@t-online.de (Norbert Schollum)
Date:
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

RE: Re: Problems with Acess

From
Michael Davis
Date:
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@t-online.de]
Sent:    Friday, March 16, 2001 2:32 PM
To:    pgsql-odbc@postgresql.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


Re: Re: Problems with Acess

From
Schollum@t-online.de (Norbert Schollum)
Date:
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@t-online.de]
> Sent:   Friday, March 16, 2001 2:32 PM
> To:     pgsql-odbc@postgresql.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

Attachment

RE: Re: Problems with Acess

From
Michael Davis
Date:
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@t-online.de]
Sent:    Friday, March 16, 2001 2:57 PM
To:    pgsql-odbc@postgresql.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@t-online.de]
> Sent:   Friday, March 16, 2001 2:32 PM
> To:     pgsql-odbc@postgresql.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


Re: Re: Problems with Acess

From
Tom Lane
Date:
Schollum@t-online.de (Norbert Schollum) writes:
> i cant find any hint in this file.
> the transaction is stopped by Rollback.
> it would be interesting, what Postgres is telling Access ....

I agree, a pretty unhelpful log.  Try running the postmaster with -d2
(and without -S) and see what gets logged in its stderr output.  You
should see all the queries and error messages.

            regards, tom lane

AW: Re: Problems with Acess

From
"Michael Moehle"
Date:
For newest odbc-driver look at
:http://www.greatbridge.org/project/pgadmin/projdisplay.php
Very good Access Faq at : http://www.scw.org/pgaccess/faq.html


M.Moehle

MBD-Team Bordesholm
Bahnhofstrasse 41
24582 Bordesholm
m.moehle@nikocity.de

-----Ursprungliche Nachricht-----
Von: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org]Im Auftrag von Norbert Schollum
Gesendet: Freitag, 16. Marz 2001 22:57
An: pgsql-odbc@postgresql.org
Betreff: Re: [ODBC] 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@t-online.de]
> Sent:   Friday, March 16, 2001 2:32 PM
> To:     pgsql-odbc@postgresql.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


Re: AW: Re: Problems with Acess

From
Thomas Lockhart
Date:
> For newest odbc-driver look at...

That would seem to be a pgadmin site, and for ODBC just provides a
click-through to the main PostgreSQL development site which is the
repository for the ODBC code. Y'all may want to just go there directly:

  http://www.postgresql.org/software.html

                       - Thomas

RE: Re: Problems with Acess

From
"Hiroshi Inoue"
Date:
Aren't art_ek, art_old_ek etc of type numeric ? If so the latest
ODBC driver would solve your problem.
Try the ODBC driver at http://www.greatbridge.org/project/pgadmin/.

ragards,
Hiroshi Inoue

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Norbert Schollum
> Sent: Saturday, March 17, 2001 6:57 AM
> To: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] 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.
>


Re: Re: Problems with Acess

From
Schollum@t-online.de (Norbert Schollum)
Date:
hi all!

the new ODBC-Driver solves the prob!! thanks a lot.

yesterday i was building my databases with mysql -
but i recognized today, that mysql is not very
professional - no triggers, no foreign keys...

thanks god it works now!!



Hiroshi Inoue wrote:
>
> Aren't art_ek, art_old_ek etc of type numeric ? If so the latest
> ODBC driver would solve your problem.
> Try the ODBC driver at http://www.greatbridge.org/project/pgadmin/.
>
> ragards,
> Hiroshi Inoue
>
> > -----Original Message-----
> > From: pgsql-odbc-owner@postgresql.org
> > [mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Norbert Schollum
> > Sent: Saturday, March 17, 2001 6:57 AM
> > To: pgsql-odbc@postgresql.org
> > Subject: Re: [ODBC] 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.
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

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

AW: Re: Problems with Acess

From
"Michael Moehle"
Date:
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.moehle@nikocity.de

-----Ursprungliche Nachricht-----
Von: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org]Im Auftrag von Michael Davis
Gesendet: Freitag, 16. Marz 2001 22:35
An: 'boopet@web.de'; pgsql-odbc@postgresql.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@t-online.de]
Sent:    Friday, March 16, 2001 2:57 PM
To:    pgsql-odbc@postgresql.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@t-online.de]
> Sent:   Friday, March 16, 2001 2:32 PM
> To:     pgsql-odbc@postgresql.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@postgresql.org so that your
message can get through to the mailing list cleanly


RE: Re: Problems with Acess

From
"Henshall, Stuart - WCP"
Date:
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@t-online.de [SMTP:Schollum@t-online.de]
> Sent:    Friday, March 16, 2001 9:57 PM
> To:    pgsql-odbc@postgresql.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@t-online.de]
> > Sent:   Friday, March 16, 2001 2:32 PM
> > To:     pgsql-odbc@postgresql.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 >>