Re: [INTERFACES] PostODBC/MS ADO

Dave Page wrote:

> Hi,
>
> This message is mainly intended for Byron (for obvious reasons) but any
> suggestions would be helpful.
>
> I'm starting to use MS ADO under VB6 for the continuing development of
> pgAdmin to allow the use of some of it's new controls like the DataRepeater.
> I can create recordsets from the data source quite successfully, but if I
> try to update them, I invariably get an error along the lines of
> 'Insufficient base table information for updating or refreshing'.

> The attached commlog does show a number of conn errors - do I have a setting
> wrong somewhere or does the driver really not support an option that is
> required for ADO?
>

Yes, there are several areas the driver does not support. However, I have been in the
middle of *EXTENSIVE* additions to the driver. These include, Multi row-wise and
column-wise binding support (instead of just 1 column-wise binding), with extensive work on
SQLExtendedFetch. This is one area that was erroring out in the log you sent me. I am
also redoing the way options are set and retrieved for SQLSetStmtOption and
SQLSetConnectOption. This should help you out also.

> On another note Byron, is there any chance of you adding an option to select
> the old style commlog (single file instead of 1 per session). It's
> frustrating during development when I have to hunt through the 15 or so
> files already created in a morning to find the one I want!!
>

I felt the same way at first. But it is useful, because even in Windows, applications were
writing all over each other's log files. If you sort by date in Explorer and do a refresh
before you look at the log files, the latest one will be right at the top of the list. I
don't know if that is useful to you or not.

Byron