Hey Dave,
Ok i reinstalled the MDAC, and the same thing happened in a different
application. Here's what seemed to cause it. I think it's limited to VB6,
i have not tried this on a production database/program yet.
I close VB6
I Open PGAdmin-2 (the stable release)
I modify the table in some way with PGA-2 in both of my cases it was to add
a column, the other was to rename a column
save the changes
open VB6 and try to run the rs.open"hodeyhodeyhodeyho" (sorry, listening to
cab calloway right now ;)) line i get the same access violation.
So, i go drop the table, and recreate it in PGAdmin-2 and viola it runs
fine.
Weird eh?
Is there any information I can provide to the developers that would help?
thank you
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.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
