Thread: RE: [GENERAL] Postgres connect with Access

> Re: Read-only tables/recordsets in Access

(1) Have you tried using psql on the Win32 machine? This will let us
know
whether your permissions are correct for editing from the other
machine.

(2) Have you tried using another ODBC client (such as MS Query)?
This will let us know whether its Access v ODBC.

(3) Are you sure that Access is properly recognizing your primary
key? (check the table design if unsure.) No primary key = No
updating of records.

(4) Do you have the READ ONLY option in the ODBC data source
turned off? The default is to leave it on. Check in *both* places in
the data source. (If you examine the table properties for the linked
table, you can see the Connect string, which will show READONLY=0
or 1 for this setting.)

--

There is a draft of a FAQ for PostgreSQL + Access at
www.scw.org/pgaccess. This may be helpful for other questions.


P.S. This question is better suited for the psql-interface mailing list,
which covers ODBC and other interfaces.
--
Joel Burton, Director of Information Systems -*- jburton@scw.org
Support Center of Washington (www.scw.org)

Hello.

I am having a couple of problems. One is that when I attempt to link SOME 
tables to access I get an error messages about an index containing a non 
existing field (an empty string). The other is that when I attempt to link 
a view as a table I get the following error.

ERROR: system column xmin not available - vievname is a view (#1)

I strongly suspect that the first error is due to the fact that I changed 
the NAMEDATALEN in the source when I compiled postgres. I suspect that the 
ODBC driver is not expecting a large string and is getting one. Could the 
second problem be related? Also is it possible to compile the ODBC drivers 
with a similar DEFINE?

Right now the NAMEDATALEN is set to 64. Although this is still small 
compared to access It's a more sane option then 32 for me.

:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/   Americas Background 
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered 
the risks of a bad hire.