Skip site navigation (1) Skip section navigation (2)

RE: RV: no updateable recordset

From: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
To: 'Manuel Martínez Valls' <mmartinezv(at)sanostra(dot)es>, Paja <paja(dot)ciambella(at)blic(dot)net>, pgsql-odbc(at)postgresql(dot)org
Subject: RE: RV: no updateable recordset
Date: 2001-06-21 08:27:31
Message-ID: E2870D8CE1CCD311BAF50008C71EDE8E01F745F5@MAIL_EXCHANGE (view raw or flat)
Thread:
Lists: pgsql-odbc
Are you using MS Access 2K? IIRC it uses ADO as default. There was a report
that ADO in MS Access couldn't be updated without OLE DB and MS DataShape
(which surprise, surprise SQL Server supports). If this is the case use DAO
instead. Make sure both read only flags are unset.
- Stuart

> -----Original Message-----
> From:	Manuel Martínez Valls [SMTP:mmartinezv(at)sanostra(dot)es]
> Sent:	Monday, June 18, 2001 9:43 AM
> To:	Paja; pgsql-odbc(at)postgresql(dot)org
> Subject:	RE: 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)
> 

pgsql-odbc by date

Next:From: DI HasenöhrlDate: 2001-06-21 08:59:41
Subject: Difference between insert by a function and per hand
Previous:From: Dave PageDate: 2001-06-21 07:30:35
Subject: RE: RV: no updateable recordset

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group