From: | Dave Millen <dave(at)largesalad(dot)co(dot)uk> |
---|---|
To: | Markus Wagner <wagner(at)imsd(dot)uni-mainz(dot)de> |
Cc: | "pgsql-interfaces(at)postgresql(dot)org" <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: pg 7.x and Access 2000 -> #deleted error |
Date: | 2001-01-22 17:54:53 |
Message-ID: | 3A6C73ED.6A09FDD7@largesalad.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hi,
This is usually fixed by ensuring that your tables have both a primary
key
and a timestamp field.
regards,
Dave
Ned Lilly wrote:
> Hi Markus,
>
> I think this is an Access issue - I seem to recall having the same
> problem with an Access front-end to Oracle a year or so ago.
>
> Regards,
> Ned
>
> Markus Wagner wrote:
>
> > Hi,
> >
> > I am using pg 7.x as a db server and MS Access should be the frontend
> > for windows clients. I installed the newest ODBC driver on the windows
> > machine. I can link in and open tables from the pg server. But when I
> > make changes/inserts, all fields of the current record will contain
> > "#deleted". I have to close and reopen the table to see the newly
> > entered/changed data.
> >
> > Any hints to get this working?
> >
> > Thanks,
> >
> > Markus
> >
> >
>
> --
> ----------------------------------------------------
> Ned Lilly e: ned(at)greatbridge(dot)com
> Vice President w: www.greatbridge.com
> Evangelism / Hacker Relations v: 757.233.5523
> Great Bridge, LLC f: 757.233.5555
--
He was part of my dream, of course -- but then I was part of his dream
too.
-- Lewis Carroll
email: dave(at)largesalad(dot)co(dot)uk
web1 : www.largesalad.co.uk
web2 : www.p21.co.uk
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Davis | 2001-01-22 17:58:56 | RE: extremely newbie questions |
Previous Message | Michael Davis | 2001-01-22 17:51:11 | RE: pg 7.x and Access 2000 -> #deleted error |