Does anyone happen to know if the unicode server compared to the non-unicode server is
faster, slower or indifferent? I'm trying to squeeze every bit of performance for my
particular app. Also, if I am targeting English only (definitely not any Asian languages)
is there any benefit to using the unicode server even though unicode is native to .Net?
The app is a C# app and I've been migrating to the ElevateDB Unicode server but I'm not
100% sure that's the most practical route for me.

Thanks


jr

James Relyea wrote:

> Also, if I am targeting English only (definitely not any Asian
> languages) ...

Maybe you *can* be that positive.  I used to be .. until I got an
email with some screenshots of my App along with a polite request to
fix the CHARSET errors!  

Malcolm
--

That's a pretty good point. I hadn't thought of anyone using an application written
entirely in English and using it to accept non-English data entry.

I think I might try to avoid a simliar email

I am still interested about the performance diffs though.


jr

James,

<< Does anyone happen to know if the unicode server compared to the
non-unicode server is faster, slower or indifferent? I'm trying to squeeze
every bit of performance for my particular app. Also, if I am targeting
English only (definitely not any Asian languages) is there any benefit to
using the unicode server even though unicode is native to .Net? The app is a
C# app and I've been migrating to the ElevateDB Unicode server but I'm not
100% sure that's the most practical route for me. >>

If you're using C#, then you have to use the Unicode ElevateDB Server, so
the performance is somewhat secondary.  Having said that, however, you
shouldn't see any major difference either way.  The Windows API is actually
100% Unicode, so the Unicode ElevateDB Server should actually experience
slightly faster API calls because no translation has to occur for
AnsiStrings during those API calls.

--
Tim Young
Elevate Software
www.elevatesoft.com