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

From Stefanos Karasavvidis
Subject Re: link tables with VB from Access fails with 7.3.01 Unicode
Date
Msg-id 3F97E41D.9060004@msc.gr
Whole thread Raw
In response to Re: link tables with VB from Access fails with 7.3.01 Unicode  ("Jean Huveneers" <j.huveneers@xillion.nl>)
Responses Re: link tables with VB from Access fails with 7.3.01 Unicode  ("Jean Huveneers" <j.huveneers@xillion.nl>)
List pgsql-odbc
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;TrueIsMinus1=1;Updat
> ableCursors=1;
> CACHESIZE=100;MAXLONGVARCHARSIZE=65536;OPTIMIZER=1;KSQO=1;USEDECLAREFETCH=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
>
>
>>-----Original Message-----
>>From: Stefanos Karasavvidis [mailto:stefos@msc.gr]
>>Sent: donderdag 23 oktober 2003 14:39
>>To: pgsql-odbc@postgresql.org
>>Subject: Re: [ODBC] link tables with VB from Access fails with 7.3.01
>>Unicode
>>
>>
>>as I haven't got any answer to this message just a note that the
>>problems I describe are still present in the new version
>>
>>7.03.0200
>>as well as
>>7.03.0201
>>
>>I would greatly appreciate if anyone could give me some idea
>>on how to
>>workaround this
>>
>>
>>Stefanos Karasavvidis wrote:
>>
>>
>>>I have 2 problems with the 7.3.01 Unicode Beta (as well as
>>
>>7.1.0115 from
>>
>>>http://www.geocities.jp/inocchichichi/psqlodbc/)
>>>
>>>I have
>>>MS Access 2000 on windows 2000 with latest MDAC
>>>Postgres 7.3.4 on Linux
>>>
>>>I use the following VB code within MS Access to link a
>>
>>table without
>>
>>>having a DSN
>>>  Set db = CurrentDb()
>>>  strConnect = "ODBC;DRIVER={PostgreSQL Unicode (Beta)};DATABASE=" +
>>>    DB_NAME + ";SERVER=" + IP_ADDRESS + ";PORT=5433;UID=" +
>>>    LOGIN + ";PWD=" + PASSWORD +
>>>    ";A6=;A7=100;A8=4096;B0=254;B1=8190;BI=0;C2=dd_;CX=188103ab"
>>>
>>>    Set tdef = db.CreateTableDef("xxxx")
>>>    tdef.Connect = strConnect
>>>    tdef.SourceTableName = "yyyyyy"
>>>    db.TableDefs.Append tdef
>>>
>>>This worked perfectly with the previous versions of the
>>
>>drivers. Now I
>>
>>>have the following problems:
>>>
>>>Problem 1
>>>==========
>>>With both drivers the above code initially fails. 7.3.01
>>
>>reports a 7711
>>
>>>error and versions 7.1.0115 Run-time error '3151'
>>>
>>>Iff I manually link any table with a DSN datasource and
>>
>>rerun the above
>>
>>>code, it works perfectly (except the other problem I will
>>
>>describe later).
>>
>>>When I close Access and reopen it, I have again the same
>>
>>problem. if I
>>
>>>don't link manually a table, the code does not work
>>>
>>>Problem 2
>>>==========
>>>although I specify CX=188103ab in the connection parameter,
>>
>>I get always
>>
>>>CX=1b503ab in the actually linked tables. In my specific
>>
>>case this does
>>
>>>not handle -1 as true.
>>>
>>>
>>>Does any oneone have a workaround or a solution for this problems?
>>>
>>>Regards
>>>
>>>Stefanos
>>>
>>
>>--
>>======================================================================
>>Stefanos Karasavvidis
>>Electronic & Computer Engineer
>>e-mail : stefos@msc.gr
>>
>>Multimedia Systems Center S.A.
>>Kissamou 178
>>73100 Chania - Crete - Hellas
>>http://www.msc.gr
>>
>>Tel : +30 2821 0 88447
>>Fax : +30 2821 0 88427
>>
>>
>>---------------------------(end of
>>broadcast)---------------------------
>>TIP 3: if posting/reading through Usenet, please send an appropriate
>>      subscribe-nomail command to majordomo@postgresql.org so
>>that your
>>      message can get through to the mailing list cleanly
>>
>>
>
>
>

--
======================================================================
Stefanos Karasavvidis
Electronic & Computer Engineer
e-mail : stefos@msc.gr

Multimedia Systems Center S.A.
Kissamou 178
73100 Chania - Crete - Hellas
http://www.msc.gr

Tel : +30 2821 0 88447
Fax : +30 2821 0 88427


pgsql-odbc by date:

Previous
From: "Jean Huveneers"
Date:
Subject: Re: link tables with VB from Access fails with 7.3.01 Unicode
Next
From: "Jean Huveneers"
Date:
Subject: Re: link tables with VB from Access fails with 7.3.01 Unicode