ODBC read/write permission in MS Access

Started by Jason Turnerover 24 years ago4 messagesgeneral
Jump to latest
#1Jason Turner
jasont@indigoindustrial.co.nz

Not sure if this should be here or in the ODBC list (that one
looked more developer-ish, wheras this list seems more admin-ish.
anyway....)

Testbedding an MS Access client to a PostgreSQL database, running
v 7.1.2 postgreSQL, Access 2000 on a Windows 2000 box. Got the driver,
version 7.1.0006. Worked like a treat, *except* for trying change
records on the Access end. The table is linked in Access via
"File->Get External Data->Link Tables". Not sure what I did wrong.
When I set up the DSN, I checked the options "Driver->Read Only"
(unchecked) and "Data Source->Read Only" (unchecked).
What did I miss?

Jason
--
Indigo Industrial Controls Ltd.
64-21-343-545
jasont@indigoindustrial.co.nz

#2Joel Burton
jburton@scw.org
In reply to: Jason Turner (#1)
Re: ODBC read/write permission in MS Access

On Tue, 31 Jul 2001, Jason Turner wrote:

Not sure if this should be here or in the ODBC list (that one
looked more developer-ish, wheras this list seems more admin-ish.
anyway....)

Testbedding an MS Access client to a PostgreSQL database, running
v 7.1.2 postgreSQL, Access 2000 on a Windows 2000 box. Got the driver,
version 7.1.0006. Worked like a treat, *except* for trying change
records on the Access end. The table is linked in Access via
"File->Get External Data->Link Tables". Not sure what I did wrong.
When I set up the DSN, I checked the options "Driver->Read Only"
(unchecked) and "Data Source->Read Only" (unchecked).
What did I miss?

What exact error message are you getting?

Have you looked at the PostgreSQL + Access FAQ at odbc.postgresql.org?

--
Joel Burton <jburton@scw.org>
Director of Information Systems, Support Center of Washington

#3Noname
wsheldah@lexmark.com
In reply to: Joel Burton (#2)
Re: ODBC read/write permission in MS Access

Check to see that the user you specified in the Windows DSN has all the
permissions in PostgreSQL it should have to do the updates. Is Access telling
you that you have a non-updatable recordset? If so, I think the online help has
a set of troubleshooting steps to work through.

Long term, you might consider using unbound forms that use select statements to
fill out the form in its On Load event, and insert/update statements to update
the back end on the appropriate On Update, etc. events. Locks won't be held as
long, you'll get to do programmatic error checking and error handling which
could make it more user-friendly, etc. etc.

Jason Turner <jasont%indigoindustrial.co.nz@interlock.lexmark.com> on 07/30/2001
08:22:32 PM

To: pgsql-general%postgresql.org@interlock.lexmark.com
cc: (bcc: Wesley Sheldahl/Lex/Lexmark)
Subject: [GENERAL] ODBC read/write permission in MS Access

Not sure if this should be here or in the ODBC list (that one
looked more developer-ish, wheras this list seems more admin-ish.
anyway....)

Testbedding an MS Access client to a PostgreSQL database, running
v 7.1.2 postgreSQL, Access 2000 on a Windows 2000 box. Got the driver,
version 7.1.0006. Worked like a treat, *except* for trying change
records on the Access end. The table is linked in Access via
"File->Get External Data->Link Tables". Not sure what I did wrong.
When I set up the DSN, I checked the options "Driver->Read Only"
(unchecked) and "Data Source->Read Only" (unchecked).
What did I miss?

Jason
--
Indigo Industrial Controls Ltd.
64-21-343-545
jasont@indigoindustrial.co.nz

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

#4Joel Burton
jburton@scw.org
In reply to: Noname (#3)
Re: ODBC read/write permission in MS Access

On Tue, 31 Jul 2001 wsheldah@lexmark.com wrote:

Check to see that the user you specified in the Windows DSN has all the
permissions in PostgreSQL it should have to do the updates. Is Access telling
you that you have a non-updatable recordset? If so, I think the online help has
a set of troubleshooting steps to work through.

Long term, you might consider using unbound forms that use select statements to
fill out the form in its On Load event, and insert/update statements to update
the back end on the appropriate On Update, etc. events. Locks won't be held as
long, you'll get to do programmatic error checking and error handling which
could make it more user-friendly, etc. etc.

or search google or the archives for "half-bound" forms, where I explain
strong compromise to bound/unbound forms.

--
Joel Burton <jburton@scw.org>
Director of Information Systems, Support Center of Washington