Yes, that did the trick for using this driver for my "Text" columns.
Thanks!

Do you have any idea on how I can transport MSSQL type Image (just bytes
internally) to a bytea column in Postgre? I'm willing to change types
around.

Thanks,
Daniel Holm


-----Original Message-----
From: Hiroshi Saito [mailto:saito@inetrt.skcapi.co.jp]
-----Original Message-----
From: "Daniel Holm"

> Attached is the new mylog and psqlodbc log for the 07.03.0261 DLL.
>
> I received the same EXCEPTION_ACCESS_VIOLATION
>
> This DLL seems to work fine with regular data types (varchar, int)

Though it is necessary to pursue, does the following definition help
you?

CREATE DOMAIN lo AS int4;

Regards,
Hiroshi Saito





---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Daniel Holm wrote:
> Yes, that did the trick for using this driver for my "Text" columns.

Hmm, it seems strange. LO has nothing to do with the text field.
Could you send me the mylog output when the driver works ?

> Thanks!
>
> Do you have any idea on how I can transport MSSQL type Image (just bytes
> internally) to a bytea column in Postgre? I'm willing to change types
> around.

You can turn on the *bytea as LO* option.

regards,
Hiroshi Inoue


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match