From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'tbyrnes(at)helioshealth(dot)com'" <tbyrnes(at)helioshealth(dot)com> |
Cc: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | RE: [INTERFACES] ODBC: 'Insufficient base table information for u pdating or refreshing' error with ADO |
Date: | 1999-10-18 08:39:35 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D6014289@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Thanks Tom. Using Server Side cursors solves the immediate problem (as long
as I remember not to put a semi colon on then end of the query!).
Unfortunately though, this means that the recordset must be refreshed to
view newly added records which is not the case when using Client Side
cursors with a command type of Table. Anyone got any ideas?
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!
> -----Original Message-----
> From: Thomas Byrnes [mailto:tbyrnes(at)helioshealth(dot)com]
> Sent: 15 October 1999 18:13
> To: 'Dave Page'; 'pgsql-interfaces(at)postgresql(dot)org'
> Subject: RE: [INTERFACES] ODBC: 'Insufficient base table
> information for
> updating or refreshing' error with ADO
>
>
> Dave,
> Are you locking the record set directly with ADO? If
> so, it may just be a
> cursor problem.
>
> Regards,
>
> Tom
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Parkinson | 1999-10-18 11:41:30 | |
Previous Message | Hiroshi Inoue | 1999-10-18 08:29:33 | RE: [INTERFACES] Table viewer for big sorted tables |