Re: Visual Basic and PostgreSQL ODBC

----- Original Message -----
From: "Mr. Shannon Aldinger" <god(at)yinyang(dot)hjsoft(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Saturday, July 28, 2001 7:32 AM
Subject: Re: [GENERAL] Visual Basic and PostgreSQL ODBC

> -----BEGIN PGP SIGNED MESSAGE-----
(...)
> Two solutions use .EOF or .BOF on your recordset, or .MoveLast, get the
> .RecordCount, then a .MoveFirst. If you don't do the .MoveLast the record
> count tends to stay at it's last value or one. This should get you on the
> right track, note I haven't tried this with postgresql as a backend, but
> it's what you have to do with MS backends.
(...)

Hi,
I have done some work with visual basic for Applications (Excel and Acces).
And ... it's horrible.
The .RecordCount in Excel is set right, when opening the Recordset an it's
updated, when inserting or deleting records.
With Access .RecordCount defaults to 0 after the recordset is created. I had
do .MoveLast to get the correct number. Furthermore .RecordCount is not
updated on .delete or .insert.
This happens with PostgreSQL and Oracle-datasouces.
So I use only .EOF to test, if there are records or not.

BTW: I hate this MS-Stuff for different behaviour in different application,
where it should behave the same way. But management says "It's our standard
... do it with MS" .... I'm very happy, i was allowed to use the
very-non-standard PostgreSQL :-)

Andre