pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Davies <scldad@sdc.com.au>
To: Sbragion Denis <infotecn@tin.it>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Odbc and Visual Basic
Date: Mon, 27 Apr 1998 18:11:05 +0930
Message-ID: <199804270841.SAA18020@mustang.sdc.com.au> (raw)
In-Reply-To: <3.0.5.32.19980427102627.008acaa0@MBox.InfoTecna.com>


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





view thread (8+ messages)  latest in thread

Message-ID: <199804270841.SAA18020@mustang.sdc.com.au>
Permalink:  ../199804270841.SAA18020@mustang.sdc.com.au/
Also on:    postgresql.org/message-id/199804270841.SAA18020@mustang.sdc.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: scldad@sdc.com.au, infotecn@tin.it
  Subject: Re: [INTERFACES] Odbc and Visual Basic
  In-Reply-To: <199804270841.SAA18020@mustang.sdc.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox