ODBC Locking troubles

From: Valerio Santinelli <tanis(at)mediacom(dot)it>
To: pgsql-interfaces(at)postgreSQL(dot)org
Subject: ODBC Locking troubles
Date: 1999-02-01 12:00:03
Message-ID: 36B5B363.D8082D12@mediacom.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

I'm still messing around with MSAccess as interface for my PostgreSQL
database and I've found out something interesting.

When trying to access some data to update in a simple table (just a
serial and 4 columns of various types) I noticed that when I try to do
an update on any of the records from a form or directly from the table,
MSAccess is saying that another user is locking that record and cannot
update it. Obviously that's not true since that's the only task
accessing the database right now.

This doesn't happen if you created the record directly from the table
screen instead of the form.

And another funny thing is that I tried this stuff under Win95 in my
office at work.
The other day I decided to bring the mdb home to try it out from here
and what I found out is that on my system running Win98 it's working
perfectly without any problem at all.

Now I'm thinking it's an ODBC problem and I should update some drivers
on my work's machine but I already tried installing the new DAO and ODBC
stuff from Visual Studio 6 Suite but nothing changed. Any idea ? Anybody
happened to notice this strange behaviour ?

Thanks in advance!

--

C'ya!

Valerio Santinelli a.k.a. TANiS
[tanis(at)mediacom(dot)it]+:+[http://www.mediacom.it/~tanis]

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Gregory W Burnham 1999-02-01 12:01:21 Re: [INTERFACES] Large objects, why not use the filesystem?
Previous Message Urban Widmark 1999-02-01 08:57:27 Re: [INTERFACES] ResultSet.getDate