From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Access, ODBC and "other users" |
Date: | 2003-11-05 14:26:12 |
Message-ID: | 200311050626.12909.aklaver@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Tuesday 04 November 2003 03:05 pm, you wrote:
> > 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
You might want to take a look at the following URL. It addresses this issue
http://techdocs.postgresql.org/guides/MSAccess#50
--
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas =?iso-8859-1?q?Sk=E4re?= | 2003-11-05 17:28:19 | bug in EN_set_odbc3 macro |
Previous Message | Theodore Petrosky | 2003-11-05 12:33:57 | help with OSX make problem |