Re: VBA 6 crashes with WIN2K, Postgres 8.1, why ? whichdll ??

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Campbell, Greg
> Sent: 06 January 2006 23:44
> To: linuxgps
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] VBA 6 crashes with WIN2K, Postgres 8.1,
> why ? whichdll ??
>
> 3. Again this is a personal preference, but I always use
> connection.Execute for INSERTS,UPDATE, and
> DELETES. Your example used on AddNew and one cnn.Execute.
>
> 4. I find a object referencing style and stick with it.
> rs.Fields("fieldname") and rs!fieldname are both a
> little dated. rs("fieldname"), or
> rs(variable_holding_field_name) or rs(integer_field_ndx) seem to be
> cultural standards now.

The example is from the psqlODBC VB HOWTO which goes out of it's way to
show the different ways to use ADO with PostgreSQL. Your suggestions are
correct of course, but there is good reason why that code looks as it
does.

> Oh, and PostgreSQL via ODBC,...
> it has never been strong on the updateable cursor/dynamic
> cursor thing.

Don't mix the two up, they are separate things. Dynamic recordsets
(adOpenDynamic) have worked well since at least 1997 when I first wrote
pgAdmin I in VB5, long before Hiroshi added the Updateable Cursors
option to the driver (back when Byron maintained it in fact). They still
do work well with the current versions of the driver (at least, none of
my users of 4 of 5 different VB apps complained when they got upgraded).
The Updateable Cursor option is an experimental implementation of
emulated updateable server-side cursors (which PostgreSQL doesn't
natively support) iirc.

Regards, Dave.