Dave,Are you locking the record set directly with ADO? If so, it may just be a
cursor problem.
Regards,
Tom
-----Original Message-----
From: owner-pgsql-interfaces@postgreSQL.org
[mailto:owner-pgsql-interfaces@postgreSQL.org] On Behalf Of Dave Page
Sent: Friday, October 15, 1999 11:16 AM
To: 'pgsql-interfaces@postgresql.org'
Subject: [INTERFACES] ODBC: 'Insufficient base table information for
updating or refreshing' error with ADO
<< File: psqlodbc.log >> Having migrated pgAdmin and some of my other apps
to ADO from DAO, I am now
getting an "Insufficient base table information for updating or refreshing"
error under certain circumstances when trying to edit a recordset. My first
experiments with ADO had a similar problem which Byron fixed - I believe ADO
was requesting extended info that the driver couldn't supply.
The current problem occurs when an update, add or delete is attemped, if
the ADO command type is text (eg. an SQL query), but not if the command type
is table (eg. you just give ADO a table name).
The attached log created with a test program which executed a 'SELECT oid, *
FROM ca_event;' and then attempted to delete the first record that was
returned in the recordset. I do have the associated ODBC trace log as well
if required, but the listserver bounced it so I'll have to mail it to anyone
who may need it.
Thanks in advance for any help...
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
<<psqlodbc.log>>
