RE: RV: no updateable recordset

From: Manuel Martínez Valls <mmartinezv(at)sanostra(dot)es>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: RE: RV: no updateable recordset
Date: 2001-06-21 07:23:24
Message-ID: NFBBLONJBDILGHLJNCHDEEMCCBAA.mmartinezv@sanostra.es
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Sorry, I've already solved the problem. The solution is just to create the
MSysConf table but... I made a mistake, I was using the 'snapshot' option on
visdata and the data were obviously 'Not Updateable'.

Thanks for your help,

Manuel Martínez Valls

-----Mensaje original-----
De: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org]En nombre de Manuel Martínez
Valls
Enviado el: lunes 18 de junio de 2001 10:43
Para: Paja; pgsql-odbc(at)postgresql(dot)org
Asunto: RE: [ODBC] RV: no updateable recordset

Hi again,

I've followed your advice and I've created this table, after that reading
the PostgreSQL ODBC FAQ I've realized that they recommend to install the
pgAdmin utility, so that's what I've done.

Now I have created the msysconf table as you told me, I've the following
values:

config=101, nvalue=1, comments='Allow local storage of passwords in
attachments'
config=102, nvalue=10, comments='Background population delay'
config=103, nvalue=100, comments='Background population size'

Now, I can't see any error on the logs, but I still having the same
no-uptdateable recordsets.

Can you told me which are the magic values?

Thanks for your help,

Manuel Martínez Valls

------------------------------
1. MS JET database engine reads some ODBC settings from MSysConf table:
CREATE TABLE "msysconf" (
"config" int2 NOT NULL,
"chvalue" character varying,
"nvalue" int4,
"comments" character varying);
REVOKE ALL on "msysconf" from PUBLIC;
GRANT SELECT on "msysconf" to GROUP "odbcusers";
All ODBC users must have permission to use the SELECT statement on this
table. For correct settings look at DAO reference.
2. You need unique index to update table. Look around Recognize Unique
Indexes or Fake Index in PostgreSQL ODBC FAQ.
Regards,
Zlatko Talic.

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://www.postgresql.org/search.mpl

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2001-06-21 07:30:35 RE: RV: no updateable recordset
Previous Message Bruce Momjian 2001-06-21 01:02:21 Re: slow performance postgres 7.0.3 and odbc