OK, my first EDB question.  

unicode 2.02.b7

I have a table script including:
....
  EXECUTE IMMEDIATE 'CREATE TABLE "DiveNames"
(
"Lang"  INTEGER,
"DiveNo"  INTEGER,
"LongName"  VARCHAR(50) COLLATE "UNI",
"ShortName"  VARCHAR(30) COLLATE "UNI"
)
......

But when I insert some data using a script as follows:
....
EXECUTE IMMEDIATE 'INSERT INTO "DiveNames" VALUES (1, 405, ''Inward
2½ Somersaults'', ''Inward 2½ Somersaults'')';
EXECUTE IMMEDIATE 'INSERT INTO "DiveNames" VALUES (1, 407, ''Inward
3½ Somersaults'', ''Inward 3½ Somersaults'')';
EXECUTE IMMEDIATE 'INSERT INTO "DiveNames" VALUES (1, 409, ''Inward
4½ Somersaults'', ''Inward 4½ Somersaults'')';
....

The data in EDBManager and in the program, displays every "½"
preceded by a "Â", eg: 'Inward 3½ Somersaults'.

So where am I going wrong?  

Malcolm


--

It seems the problem is with the IDE or something.
When I open the script in the EDB Manager I see the extra character.
Hmm.....

Malcolm,

<< It seems the problem is with the IDE or something. When I open the script
in the EDB Manager I see the extra character. >>

Yeah, I'm not seeing it in the EDB Manager script window.  I'll have to
double-check the data insertion and see what I can find.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Yeah, I'm not seeing it in the EDB Manager script window.  I'll
> have to double-check the data insertion and see what I can find.

Don't worry too much about this.  I have not had the time to test it
fully, but it looks like it is a carry-over from D2006.  I saw the
same thing with accented characters.  I changed TDBISAMQuery to
EDBQuery outside the IDE (otherwise they were zapped by the IDE) and
all seemed OK but of course the .SQL ansistrings would not convert to
unicode so the new unicode component would be confused.

If I find a 'real' problem I will yell later.  

Malcolm

--