pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedrecordset not updateable
7+ messages / 4 participants
[nested] [flat]
* recordset not updateable
@ 1999-04-23 21:37 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
0 siblings, 0 replies; 7+ messages in thread
From: JT Kirkpatrick @ 1999-04-23 21:37 UTC (permalink / raw)
To: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
I am using rh 5.2, postgres 6.4.2, linking to postgres with access97 and
odbc driver. I can create a simple table, link to it, open it, and access
tell me that "this recordset is not updateable". However, I have created
many other tables in the same fashion and even much more complex and they
are just fine. Any idea what could be going on? This just started
happening today. Most of the tables I created over the past few weeks are
working fine (I met one exception which has led me to create some test
tables and link to them). BTW, I can update the table directly in psql on
the server itself with no problem, so it must be odbc or access. But why
do the other tables still work just fine? HELP!!!! Where can I look??
JT
^ permalink raw reply [nested|flat] 7+ messages in thread
* recordset not updateable
@ 1999-04-23 21:53 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
0 siblings, 1 reply; 7+ messages in thread
From: JT Kirkpatrick @ 1999-04-23 21:53 UTC (permalink / raw)
To: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
this is a resubmit with my pdbc log file. It shows an error in finding
the file MsysConf. Maybe this is the problem?? Can someone please provide
some insight? Thanks!
I am using rh 5.2, postgres 6.4.2, linking to postgres with access97 and
odbc driver. I can create a simple table, link to it, open it, and access
tell me that "this recordset is not updateable". However, I have created
many other tables in the same fashion and even much more complex and they
are just fine. Any idea what could be going on? This just started
happening today. Most of the tables I created over the past few weeks are
working fine (I met one exception which has led me to create some test
tables and link to them). BTW, I can update the table directly in psql on
the server itself with no problem, so it must be odbc or access. But why
do the other tables still work just fine? HELP!!!! Where can I look??
JT
Attachments:
psqlodbc.log (application/octet-stream, 2.7K) download
^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: [ADMIN] recordset not updateable
@ 1999-04-23 21:53 Michael J Davis <michael.j.davis@tvguide.com>
0 siblings, 0 replies; 7+ messages in thread
From: Michael J Davis @ 1999-04-23 21:53 UTC (permalink / raw)
To: 'JT Kirkpatrick' <jt-kirkpatrick@mpsllc.com>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
1) The problem is likely the user name that Access97 is using to communicate
with PostgreSQL. Turn on the logging in the PostgreSQL ODBC driver. Look
at the PostgreSQL log file in your c:\ directory after opening Access97 and
the table in question. Look in the log file and check user name that
PostgreSQL is using to connect to the server and verify that the user exists
in PostgreSQL (including case).
If you are not using Access97 security, then you will need to create an
"Admin" user in postgreSQL. The quotes and uppercase "A" are needed in the
create user statement.
Create user "Admin";
2) Also make sure the user has write permission to the table.
3) Another thing that nailed me was the unique key field. You need to turn
on Unique Key support in the PostgreSQL ODBC driver and each table you want
to update needs to have a unique key installed.
-----Original Message-----
From: JT Kirkpatrick [SMTP:jt-kirkpatrick@mpsllc.com]
Sent: Friday, April 23, 1999 3:37 PM
To: 'pgsql-interfaces@hub.org'; 'pgsql-admin@hub.org'
Subject: [ADMIN] recordset not updateable
I am using rh 5.2, postgres 6.4.2, linking to postgres with access97
and
odbc driver. I can create a simple table, link to it, open it, and
access
tell me that "this recordset is not updateable". However, I have
created
many other tables in the same fashion and even much more complex and
they
are just fine. Any idea what could be going on? This just started
happening today. Most of the tables I created over the past few
weeks are
working fine (I met one exception which has led me to create some
test
tables and link to them). BTW, I can update the table directly in
psql on
the server itself with no problem, so it must be odbc or access.
But why
do the other tables still work just fine? HELP!!!! Where can I
look??
JT
^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: [INTERFACES] recordset not updateable
@ 1999-04-24 00:35 Michael J Davis <michael.j.davis@tvguide.com>
0 siblings, 0 replies; 7+ messages in thread
From: Michael J Davis @ 1999-04-24 00:35 UTC (permalink / raw)
To: 'JT Kirkpatrick' <jt-kirkpatrick@mpsllc.com>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
No, I don't think MsysConf is the problem.
-----Original Message-----
From: JT Kirkpatrick [SMTP:jt-kirkpatrick@mpsllc.com]
Sent: Friday, April 23, 1999 3:53 PM
To: 'pgsql-interfaces@hub.org'; 'pgsql-admin@hub.org'
Subject: [INTERFACES] recordset not updateable
this is a resubmit with my pdbc log file. It shows an error in
finding
the file MsysConf. Maybe this is the problem?? Can someone please
provide
some insight? Thanks!
I am using rh 5.2, postgres 6.4.2, linking to postgres with access97
and
odbc driver. I can create a simple table, link to it, open it, and
access
tell me that "this recordset is not updateable". However, I have
created
many other tables in the same fashion and even much more complex and
they
are just fine. Any idea what could be going on? This just started
happening today. Most of the tables I created over the past few
weeks are
working fine (I met one exception which has led me to create some
test
tables and link to them). BTW, I can update the table directly in
psql on
the server itself with no problem, so it must be odbc or access.
But why
do the other tables still work just fine? HELP!!!! Where can I
look??
JT << File: psqlodbc.log >>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [INTERFACES] recordset not updateable
@ 1999-04-27 00:39 Byron Nikolaidis <byronn@insightdist.com>
parent: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
0 siblings, 0 replies; 7+ messages in thread
From: Byron Nikolaidis @ 1999-04-27 00:39 UTC (permalink / raw)
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>; +Cc: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
JT Kirkpatrick wrote:
> this is a resubmit with my pdbc log file. It shows an error in finding
> the file MsysConf. Maybe this is the problem?? Can someone please provide
> some insight? Thanks!
>
The MsysConf is NOT the problem. It is an *optional* config file for the Jet Database
engine (which Access uses).
Do you have a unique index on the table?
Check the FAQ carefully at our site also: http://www.insightdist.com/psqlodbc
Also, you may want to upgrade the odbc driver also. Your version is 6.30.0250 and the
newest is 6.40.0005 or something like that.
Byron
^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: [INTERFACES] recordset not updateable
@ 1999-04-27 15:49 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
0 siblings, 0 replies; 7+ messages in thread
From: JT Kirkpatrick @ 1999-04-27 15:49 UTC (permalink / raw)
To: 'Byron Nikolaidis' <byronn@insightdist.com>; JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>; +Cc: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
I'll upgrade the odbc driver, but this version seems to be working on the
other tables. To answer your question about a unique index, NO. have I
missed it?? Does every table need a unique index for the odbc driver to
work properly??
jt
-----Original Message-----
From: Byron Nikolaidis [SMTP:byronn@insightdist.com]
Sent: Monday, April 26, 1999 8:40 PM
To: JT Kirkpatrick
Cc: 'pgsql-interfaces@hub.org'; 'pgsql-admin@hub.org'
Subject: Re: [INTERFACES] recordset not updateable
JT Kirkpatrick wrote:
> this is a resubmit with my pdbc log file. It shows an error in finding
> the file MsysConf. Maybe this is the problem?? Can someone please
provide
> some insight? Thanks!
>
The MsysConf is NOT the problem. It is an *optional* config file for the
Jet Database
engine (which Access uses).
Do you have a unique index on the table?
Check the FAQ carefully at our site also:
http://www.insightdist.com/psqlodbc
Also, you may want to upgrade the odbc driver also. Your version is
6.30.0250 and the
newest is 6.40.0005 or something like that.
Byron
^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: [INTERFACES] recordset not updateable
@ 1999-04-27 16:24 Ken J. Wright <ken@ori-ind.com>
0 siblings, 0 replies; 7+ messages in thread
From: Ken J. Wright @ 1999-04-27 16:24 UTC (permalink / raw)
To: pgsql-interfaces@hub.org
This is not a requirement of the odbc driver. This is a problem with
Access. It (somewhat logically) needs the unique index to identify what
record conditions to specify in the update statement it constructs. "update
blah where blah.col = blah". Otherwise every column & value in the row
would have to be declared in the "where" clause. Borland gets around it by
doing just that!
Ken
>
>I'll upgrade the odbc driver, but this version seems to be working on the
>other tables. To answer your question about a unique index, NO. have I
>missed it?? Does every table need a unique index for the odbc driver to
>work properly??
>
>jt
>
>-----Original Message-----
>From: Byron Nikolaidis [SMTP:byronn@insightdist.com]
>Sent: Monday, April 26, 1999 8:40 PM
>To: JT Kirkpatrick
>Cc: 'pgsql-interfaces@hub.org'; 'pgsql-admin@hub.org'
>Subject: Re: [INTERFACES] recordset not updateable
>
>
>
>JT Kirkpatrick wrote:
>
>> this is a resubmit with my pdbc log file. It shows an error in finding
>> the file MsysConf. Maybe this is the problem?? Can someone please
>provide
>> some insight? Thanks!
>>
>
>The MsysConf is NOT the problem. It is an *optional* config file for the
>Jet Database
>engine (which Access uses).
>
>Do you have a unique index on the table?
>
>Check the FAQ carefully at our site also:
> http://www.insightdist.com/psqlodbc
>
>Also, you may want to upgrade the odbc driver also. Your version is
>6.30.0250 and the
>newest is 6.40.0005 or something like that.
>
>Byron
>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~1999-04-27 16:24 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-04-23 21:37 recordset not updateable JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-04-23 21:53 recordset not updateable JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-04-27 00:39 ` Byron Nikolaidis <byronn@insightdist.com>
1999-04-23 21:53 RE: [ADMIN] recordset not updateable Michael J Davis <michael.j.davis@tvguide.com>
1999-04-24 00:35 RE: [INTERFACES] recordset not updateable Michael J Davis <michael.j.davis@tvguide.com>
1999-04-27 15:49 RE: [INTERFACES] recordset not updateable JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-04-27 16:24 RE: [INTERFACES] recordset not updateable Ken J. Wright <ken@ori-ind.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox