Re: link tables with VB from Access fails with 7.3.01 Unicode - Mailing list pgsql-odbc

From Jean Huveneers
Subject Re: link tables with VB from Access fails with 7.3.01 Unicode
Date
Msg-id 000301c3997a$ded9c760$470110ac@farcourier.com
Whole thread Raw
In response to Re: link tables with VB from Access fails with 7.3.01 Unicode  (Stefanos Karasavvidis <stefos@msc.gr>)
List pgsql-odbc
Hi,

My connect string are fine, problem only is the some program's use normal
string variables and they have a max lenght of 254 characters.
I use the Delphi Widestring that can take 4GB (2GB in unicode).

I read/was told that in the new 7.3.x ODBC Drivers the unicode driver is
default, and you have to specify the legacy driver if you don't want to use
unicode.
That caused some troubels in my applications too, but works fine now.

Regards,

Jean Huveneers

Xillion ICT Solutions B.V.
Marktplein 8
6243 BR  Geulle
The Netherlands

tel: +31 (0)43 3659244
fax: +31 (0)43 3659249
gsm: +31 (0)6 456 44 357
www: www.xillion.nl

> -----Original Message-----
> From: Stefanos Karasavvidis [mailto:stefos@msc.gr]
> Sent: donderdag 23 oktober 2003 16:22
> To: j.huveneers@xillion.nl; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] link tables with VB from Access fails with 7.3.01
> Unicode
>
>
> Thanks Jean for the info. I'd somewhere read that there are length
> restrictions in the connect string and that we should not use
> this kind
> of parameters, but anyway it DID NOT WORK with this either.
>
> But you use the "normal" Postgres driver and not the unicode (beta)
> driver, so maybe it is related with the driver.
>
> The issue is that it did work BEFORE version 7.03.01 so
> something in the
> new versions (7.01 and 7.02) has triggered this.
>
> Regards
>
> Stefanos
>
> Jean Huveneers wrote:
> > Hi,
> >
> > In your second problem, you name CX=xxx as a solution for
> setting true = -1?
> > I use this connect string for working with PostgreSQL unter
> Delphi 7 and
> > Access.
> >
> > Provider=MSDASQL.1;Extended
> >
> Properties="DRIVER={PostgreSQL};DATABASE={databasename};SERVER
> ={servername};
> >
> PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN
> =0;ROWVERSIONI
> > NG=0;SHOWSYSTEMTABLES=0;
> > CONNSETTINGS=SET CLIENT_ENCODING TO ''LATIN1'';
> >
> FETCH=100;SOCKET=4096;UNKNOWNSIZES=0;MAXVARCHARSIZE=254;TrueIs
> Minus1=1;Updat
> > ableCursors=1;
> >
> CACHESIZE=100;MAXLONGVARCHARSIZE=65536;OPTIMIZER=1;KSQO=1;USED
> ECLAREFETCH=0;
> > TEXTASLONGVARCHAR=0;
> >
> UNKNOWNSASLONGVARCHAR=1;BOOLSASCHAR=0;PARSE=0;CANCELASFREESTMT
> =0;EXTRASYSTAB
> > LEPREFIXES=dd_";
> > LFConversion=1;DisallowPremature=0;BI=0;
> > DEBUG=0;COMMLOG=0;
> >
> > where TrueIsMinus1=1 takes care of the right way of
> returning booleans.
> >
> > hope is helps you.
> >
> > Regards,
> >
> > Jean Huveneers
> >
> > Xillion ICT Solutions B.V.
> > Marktplein 8
> > 6243 BR  Geulle
> > The Netherlands
> >
> > tel: +31 (0)43 3659244
> > fax: +31 (0)43 3659249
> > gsm: +31 (0)6 456 44 357
> > www: www.xillion.nl
> >
> >

>
>


pgsql-odbc by date:

Previous
From: Stefanos Karasavvidis
Date:
Subject: Re: link tables with VB from Access fails with 7.3.01 Unicode
Next
From: "Dave Page"
Date:
Subject: Re: link tables with VB from Access fails with 7.3.01 Unicode