pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedVB and ODBC: found
2+ messages / 2 participants
[nested] [flat]
* VB and ODBC: found
@ 1998-04-27 10:08 Sbragion Denis <infotecn@tin.it>
1998-04-27 12:11 ` Re: [INTERFACES] VB and ODBC: found Stephen Davies <scldad@sdc.com.au>
0 siblings, 1 reply; 2+ messages in thread
From: Sbragion Denis @ 1998-04-27 10:08 UTC (permalink / raw)
To: pgsql-interfaces
Hello,
after a fast look I found a reference in the MS knowledge base:
http://support.microsoft.com/support/kb/articles/q109/8/00.asp
little excerpt:
Before you can edit an external ODBC table, the table must contain a unique
index. If you get the following error message, you might not have a unique
index on the table:
Can't perform operation; it is illegal.
You could also receive this error if the Data1.Recordset.Updatable flag is
not set to True. Also, if you set the Data1.Options property to 64
(SQL_PASSTHROUGH), the data control will not be updatable.
Hope it helps.
Bye !
Dr. Sbragion Denis
InfoTecna
Tel, Fax: +39 39 2324054
URL: http://space.tin.it/internet/dsbragio
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [INTERFACES] VB and ODBC: found
1998-04-27 10:08 VB and ODBC: found Sbragion Denis <infotecn@tin.it>
@ 1998-04-27 12:11 ` Stephen Davies <scldad@sdc.com.au>
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Davies @ 1998-04-27 12:11 UTC (permalink / raw)
To: Sbragion Denis <infotecn@tin.it>; +Cc: pgsql-interfaces
> Hello,
>
> after a fast look I found a reference in the MS knowledge base:
>
> http://support.microsoft.com/support/kb/articles/q109/8/00.asp
>
> little excerpt:
>
> Before you can edit an external ODBC table, the table must contain a unique
> index. If you get the following error message, you might not have a unique
> index on the table:
>
> Can't perform operation; it is illegal.
>
> You could also receive this error if the Data1.Recordset.Updatable flag is
> not set to True. Also, if you set the Data1.Options property to 64
> (SQL_PASSTHROUGH), the data control will not be updatable.
>
OK. Maybe that is the difference. I never use data controls to access ODBC
databases: the performance is awful.
There also seem to be strange constraints placed by MS on some types of
recordsets: the "safest" seem to be tables rather than dynasets etc.
I always use direct calls to the ODBC DLL. This is quite easy and, in general,
gives performance comparable with native SQL commands - and does not require
unique indexes or other strange MS policies..
Having said that, my personal preference is to have a unique key in every
table and if there is no obvious candidate, to make that key a
system-generated sequence number.
Cheers,
Stephen.
========================================================================
Stephen Davies Consulting scldad@sdc.com.au
Adelaide, South Australia. Voice: 61-8-82728863
Computing & Network solutions. Fax: 61-8-82741015
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1998-04-27 12:11 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-04-27 10:08 VB and ODBC: found Sbragion Denis <infotecn@tin.it>
1998-04-27 12:11 ` Stephen Davies <scldad@sdc.com.au>
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