Hi Jack,
After a great deal of testing I've found the cause of this problem. It
is caused by ADO when it finds high or very low ASCII characters in
adLongVarChar columns. The problem occured because newer versions of
pgAdmin set the ODBC drivers UnknownsAsLongVarChar option to 1 which
caused binary data to be presented as a LongVarChar.
If you'd like to test a new version (which also has some other new
features), please try the snapshot build from the binaries directory at
http://cvs.pgadmin.org/. Installation instructions are in the readme.
Regards, Dave.
> -----Original Message-----
> From: jack [mailto:datactrl@tpg.com.au]
> Sent: 03 February 2003 01:02
> To: Dave Page
> Subject: Re: [pgadmin-support] problem on view data
>
>
> Dave,
>
> Thank you for the reply. I use an old version of pgAdmin Ver
> 1.1.76 to open the same pg_index. It can open without any
> problem. So is that a problem of ADO? Would you please
> advise. Thank you!
>
> Jack
>
> ----- Original Message -----
> From: "Dave Page" <dpage@vale-housing.co.uk>
> To: "jack" <datactrl@tpg.com.au>; "pgadmin"
> <pgadmin-support@postgresql.org>
> Sent: Saturday, February 01, 2003 5:07 AM
> Subject: RE: [pgadmin-support] problem on view data
>
>
>
>
> > -----Original Message-----
> > From: jack [mailto:datactrl@tpg.com.au]
> > Sent: 31 January 2003 01:11
> > To: pgadmin
> > Subject: [pgadmin-support] problem on view data
> >
> >
> > Hi,
> >
> > Using: pgAdmin II V1.4.12
> > When view data of table pg_index, it will close down pgAdmin
> > automatically. Thank you very much !
>
> Yes, unfortunately this appears to be a problem in
> Microsoft's ADO which has trouble wit some array types. The
> pg_trigger table will do it as well iirc.
>
> Regards, Dave.
>
>
>
