the PGAdmin theory wasn't it. But, what i did find was if i did
rs.Open"SELECT field1,field2,..." instead of "SELECT * ..." it worked.
I've run into the * problem with other tables before, but those tables had
like 40 columns with real long column names. This table only had 8 columns
with modertly short column names.
So, four hours later...
I did find out it was a VB problem, my PG server was passing all requested
data back, but VB was choking on it (imagine that)
thanks for feedback, i think i've earned that new workstation ;)
corey
On Wednesday, August 07, 2002 12:51 AM, Dave Page
[SMTP:dpage@vale-housing.co.uk] wrote:
>
>
> > -----Original Message-----
> > From: Corey Gibbs [mailto:cgibbs@westmarkproducts.com]
> > Sent: 06 August 2002 18:23
> > To: pgsql-odbc@postgresql.org
> > Subject: [ODBC] ODBC driver causes VB to crash
> >
> >
> > Howdy everyone,
> >
> > think i just need to totally remove the PG odbc driver and
> > reinstall? Or
> > do i need to tell my boss i need a new workstation? ;)
>
> I'd go with the new workstation!
>
> Seriously though, it's *very* unlikely that a reinstall of psqlODBC will
> fix things - it's only one .dll and a few registry entries. Feel free to
> try though....
>
> I would be more inclined to reinstall MDAC and double check your code.
>
> Regards, Dave.