Re: Antw: Re: VBA 6 crashes with WIN2K, Postgres 8.1, why? which dll ??

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "linuxgps" <linuxgps(at)invitel(dot)hu>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Antw: Re: VBA 6 crashes with WIN2K, Postgres 8.1, why? which dll ??
Date: 2006-01-11 09:37:27
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40103D697@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: linuxgps [mailto:linuxgps(at)invitel(dot)hu]
> Sent: 09 January 2006 16:37
> To: Dave Page
> Subject: Re: Antw: Re: [ODBC] VBA 6 crashes with WIN2K,
> Postgres 8.1, why? which dll ??
>
> I've reinstalled the newest postgres v8.1.2 win32 msi
> (http://wwwmaster.postgresql.org/download/mirrors-ftp?file=bin
> ary%2Fv8.1.2%2Fwin32%2Fpostgresql-8.1.2-1.zip)
> from the pgfoundry
> http://wwwmaster.postgresql.org/download/mirrors-ftp?file=odbc
> %2Fversions%2Fdll%2Fpsqlodbc-08_01_0102.zip
> In the VB 6(SP6) the cn debugstring has the following value after the
> connection:
> debug1 Provider=MSDASQL.1;Extended
> Properties="DSN=compaq1;DATABASE=postgres;SERVER=localhost;POR
> T=5432;SSLMODE=prefer;UID=postgres;PWD=pgtest;ReadOnly=0;Proto
> col=6.4;FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSys
> temTables=0;ConnSettings=;Fetch=100;Socket=8192;UnknownSizes=0
> ;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=1;CommLog=1;
> Optimizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;Unkno
> wnsAsLongVarchar=0;BoolsAsChar=1;Parse=1;CancelAsFreeStmt=0;Ex
> traSysTablePrefixes=dd_;;LFConversion=1;UpdatableCursors=0;Dis
> allowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;Us
> eServerSidePrepare=0;LowerCaseIdentifier=0"
> stepping to next program line:

The only differences I can see are that you have commlog turned on which
I do not, and you have Parse Statements turned on, which I don't. I know
which I'd lay money on being the culprit if it is one of those, but
perhaps you could turn the options off one at a time, testing after each
one.

Other that that, I'm stumped. Perhaps someone else can run the test and
see what happens. Or maybe someone else has an idea.

It might be worth posting the full VB project you are using, just in
case there's a copy n paste error or something in it.

Regards, Dave.

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Zoltan Boszormenyi 2006-01-11 09:53:20 Re: PsqlODBC slow on UNION queries
Previous Message Ludek Finstrle 2006-01-11 09:25:33 Re: PsqlODBC slow on UNION queries