I had the the same problem using
Access form / linked pg tables
now it works with an default at the boolean field
for example the column nocalc
ALTER TABLE public.awork ALTER COLUMN nocalc DEFAULT false;
AND
don't use a timestamptz field in your
Access select statement
ALTER TABLE public.awork ADD COLUMN log_time timestamptz;
ALTER TABLE public.awork ALTER COLUMN log_time DEFAULT
"timestamp"('now'::text);
perhaps it helps
moin,
henry
-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Steve Crawford
Sent: Wednesday, November 05, 2003 12:06 AM
To: Greg Campbell; tech@murrain.net
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] Access, ODBC and "other users"
> Michelle Murrain wrote:
> > We have an interesting problem with Access and ODBC. ...
> Access then doesn't let anyone update the table, because
> > "another user has modified the data".
On Tuesday 04 November 2003 6:22 am, Greg Campbell wrote:
> My first guess has to do with transactioning. Are you using any
> type of explicit transactions (BeginTrans) that might not have
> committed or rolled back, while your overnight script was changing
> the data?
No, it's one of many oddities in Access/ODBC. Even on a small PG table
used by only one person we see this in Access. We haven't figured it
out, yet, but we know it doesn't occur on all tables. Our solution
will probably be to just phase out Access as we did with MSSQL but if
we figure it out I'll post the info.
Cheers,
Steve
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
