Re: client encoding mismatch help!

Thanks for the very fast reply Luf,

On Tuesday 13 December 2005 1:42 pm, Ludek Finstrle wrote:
> > I have installed 8.1 server on a FC4 system and loaded my
> > 7.3.2 database data (not too many problems) all is working well
> > except the odbc driver won't connect !
> > The database was built with no encoding options set, the driver
> > is psqlodbc-08_01_0102 with default options (but I have tryed many)
> >
> > The Driver Log file follows :=
>
> It seems you are trying psqlodbc on Windows. Am I right?
Yes Win2000 at the moment - Xp, 98 & ME to follow)
> It is more helpful when you post us mylog output (both - Global and
> DataSource settings).
I can't generate a log file as I don't have a C-Drive
and the logpath seems to be hard wired!
>
> Do you try ANSI or Unicode driver? Does problem exist with both types
> of psqlODBC driver?
I only saw one stable msi driver ! (but I guess I looked in the wrong place)
>
> > Please help, I need to get this system up an running in production
> > pronto ;)
>
> I hope you don't mean in 5 minutes ...
No, 2 days (luxury)
>

I have solved the connect problem by rebuilding the database with
--encoding=SQL_ANSII, I guess the database default to some other
encoding schema - I bet it's in the documentation somewhere :) this
allows the windows ODBC drivers to work (mostly) but  now
fails with my datawindow objects :( it seem the from ODBC 2 -> 3
the TIMESTAMP field has changed some how, and the datawindow
can't deal with it (first guess)!

Is there some way to force the driver/database to use the old 2.0 ODBC
format ?

Cheers,

    Frank