RE: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC - Mailing list pgsql-interfaces

From Dave Page
Subject RE: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC
Date
Msg-id 8568FC767B4AD311AC33006097BCD3D609168F@woody.vale-housing.co.uk
Whole thread Raw
List pgsql-interfaces
> -----Original Message-----
> From: Thomas Tang [mailto:tang@future.com.cn]
> Sent: 23 February 2000 08:51
> To: Dave Page
> Subject: RE: [INTERFACES] Visual Basic/Data Environment 
> Designer/PgODBC
> 
> 
> I have the same problem. I've unchecked both two settings in the
> driver(datasource and advanced), but it still didn't work. I 
> can even create
> a table, but I can not insert & update records in the table.

ADO (which I assume the Data Environment uses) will make an individual
recordset read only if you include a semi-colon at the end of the query (as
you would in psql), but won't issue an error as it (unlike DAO) assumes that
any query syntax is legal unless the remote db says otherwise. It does make
the recordset readonly though as it can't correctly parse the select to
figure out what insert/update query to issue.

This one got me when I first started using ADO as DAO though far more picky
about syntax, didn't mind the ';'.

Regards,  
Dave.  
-- 
NASA uses Windows? Oh great. If Apollo 13 went off course today
the manual would just tell them to open the airlock, flush the astronauts
out, and re-install new ones! - Kibo in the SDM.
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)  


pgsql-interfaces by date:

Previous
From: "Alexey V. Meledin"
Date:
Subject: Re[2]: [INTERFACES] Sharing Database Connection...
Next
From: Rob Brown-Bayliss
Date:
Subject: creating a db with libpq