| From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
|---|---|
| To: | "Greg Campbell" <greg(dot)campbell(at)us(dot)michelin(dot)com>, tech(at)murrain(dot)net |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Access, ODBC and "other users" |
| Date: | 2003-11-04 23:05:55 |
| Message-ID: | 200311041505.55413.scrawford@pinpointresearch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akhona Damane | 2003-11-05 06:57:21 | ODBC |
| Previous Message | Hiroshi Inoue | 2003-11-04 22:21:18 | Re: Strange error in 7.3.2.01 |