Tim


"Why do the other client and server applications have to use the non-Unicode
version of EDB ?  There's no difference in terms of performance, etc."

Please correct me if I am wrong, but in my understanding that would require controls which
support unicode.

Leslie

Leslie,

<< Please correct me if I am wrong, but in my understanding that would
require controls which support unicode. >>

Nope.  Our Unicode EDB Manager uses the ANSI VCL controls, and the
WideString <--> AnsiString conversions work seamlessly.  The Unicode is
converted to MBCS, and vice-versa, when dealing with extended character sets
like Chinese, etc.  For English, French, and other European languages, the
conversion is almost always doable with the base 256 Unicode code points,
which are the same as the 256 ANSI code points.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

"I'm not sure what you mean - INSERT INTO..SELECT *is* done internally by the
engine."

If I write the code  I need to Query the data, read it and have it inserted to the target
table with SQL inserts.  In my experience populating a Dataset like this is  much slower
then when the server directly writes the data to the target table. With small amount of
data it does not matter, but with 100000+ records ...  

"<< This one seems to require only a few lines of code ... >>

Sure, if you don't have any documentation and testing to worry about.

I know all about it.  But even all considered this one should not be a big a deal, that is
why I dared to mention it.

Leslie

Tim,

"Nope.  Our Unicode EDB Manager uses the ANSI VCL controls, and the
WideString <--> AnsiString conversions work seamlessly.  The Unicode is
converted to MBCS, and vice-versa, when dealing with extended character sets
like Chinese, etc.  For English, French, and other European languages, the
conversion is almost always doable with the base 256 Unicode code points,
which are the same as the 256 ANSI code points."

Does this mean that the DBaware controls we are using would work with the unicode version
of ElvateDB right away?

Leslie

"In my experience populating a Dataset like this is much slower
then when the server directly writes the data to the target table."

I do not mean when the server is on a different machine here. The difference I am refering
here is not the result of network transfer. That makes it much slower even if the inserts
are optimized considering the speed of the network traffic.


Leslie

Leslie,

<< If I write the code  I need to Query the data, read it and have it
inserted to the target table with SQL inserts.  In my experience populating
a Dataset like this is  much slower then when the server directly writes the
data to the target table. With small amount of data it does not matter, but
with 100000+ records ...   >>

Could you be more specific about what it is that you're trying to accomplish
?  I can make heads or tails or what it is exactly that you want to do.  A
simple INSERT INTO..SELECT FROM is all done directly on the server, in the
fastest manner possible.  If that doesn't fit your needs, then I obviously
don't have a clue as to what you're talking about.

--
Tim Young
Elevate Software
www.elevatesoft.com

Leslie,

<< Does this mean that the DBaware controls we are using would work with the
unicode version of ElvateDB right  away? >>

Sure.  That's how I got the Windows CE demo to work - it uses a normal TEdit
in the LCL (AnsiString), but the TEDBTable being used is grabbing the data
from a TWideStringField.  It works fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

INSERT INTO..SELECT FROM

Tim, I am sorry, I have completely wasted our time on this!  Have no idea how I could have
missed it, but it's been there all the time in the documention. I just did not realise
that what I needed already existed.

Leslie

Tim,

"<< Does this mean that the DBaware controls we are using would work with the
unicode version of ElvateDB right  away? >>

Sure.  That's how I got the Windows CE demo to work - it uses a normal TEdit
in the LCL (AnsiString), but the TEDBTable being used is grabbing the data
from a TWideStringField.  It works fine."

My misstake again. Have not used unicode before and for some reason I thought that unicode
data requires unicode aware controls. Glad to be wrong about it!

Leslie   

... I suppose there would  be no problem with VCL for the WEB controls either.