ODBC LongVarChar umlaut

[ghash]

Hello,

i have a problem asgain:

I want to insert text via ODBC into a LONG VARCHAR-field, which seems to work but the internal ODBC-Driver-Encoding seems to fail.
When i want to save the String
"test: a ö ü ß €"
i get in database:
"test: a ö ü ß €"

Normally i would convert the umlauts to my own keywords, but another software has also access to it, so it wont work.

I have this issue in every PHP / SQLBase - Project and cant continue without a solution.

SQLBase:.........10.0.0
ODBC-Driver:....10.0.0

is there any workaround to solve that problem?

[Jeff Luther]

What's the column type in the DB? What version of TD? Looks like a Unicode issue, though you've posted this in the Older Releases section, not the v5.2 section.

And you're inserting/fetching back from/to a Long String variable or field? And the DB column is a LONG-type column? Does it support Unicode?

[clemdoc]

Hi!

PHP / SQLBase

Maybe you should post this in the SqlBase section since it doesn't seem to have anything to do with TD.
Greetings and good luck,
clem

[ghash]

Ah, i see, i have chosen the wrong forum, it should be in "SQLBase, older Releases"

We use TD 3.0, but that have nothing to do with these projects.

The column-type is "LONG VARCHAR". If i select data from this table/field, i get the correct String. Only if i want to input or update data to this LONG VARCHAR via PHP (->ODBC), the umlauts fail. The encoding of the PHP-Script-File is ANSI, i've tried a lot so far, so i guess its a bug in the ODBC-Driver or something around. Maybe i can set up the ODBC-Settings for example charset or encoding anyhow?

[Jeff Luther]

Hi -- Sorry, I missed "LONG VARCHAR" earlier. I'm asking Mike Vandine, our SQLBase guru, to look at this thread.

[Jeff Luther]

ghash -- disregard my previous comment. I see you posted duplicate msgs. both here and (correctly) in the SQLBase sections.

KINDLY do not do that -- very confusing (as you see from my concern here and asking Mike to take a look at this.) Everyone basically sees everything and all dup. threads is confuse the issue, force multiple comments that aren't together.

Looks like Mike responded to your other thread.