infotecn@tin.it said:
> One of the things that prevents wider use of PostODBC under Visual
> Basic (at least v. 5.0) is the lack of a good index support in the
> ODBC driver itself. Visual Basic requires that at least one unique
> index should be available on a table to allow updates. Currently this
> is circumvented using an Access database with all the tables linked in
> it and specifying at the Access level wich is the unique key for the
> tables. Anyway, to use the Visual Basic ODBCDirect functionality true
> index support is required to allow udpates. Is it difficult to
> implement it ?
I don't quite follow this.
I have VB5 apps which update PostgreSQL tables which do not have unique
indexes. The same apps work under VB4 as well and with both the old and new
ODBC drivers.
I have never tried the Access route (and never will) but understood that the
unique index problem was an Access thing rather than VB.
Does anyone have any pointers to canonical statements on this?
Cheers and thanks,
Stephen.
========================================================================
Stephen Davies Consulting scldad@sdc.com.au
Adelaide, South Australia. Voice: 61-8-82728863
Computing & Network solutions. Fax: 61-8-82741015