I'm currently using DBISAM 4 and Delphi 5.

Does ElevateDB support unicode?

I have an application using a DBISAM database, there is one string field in the database I
want to convert to unicode/widestring. So assuming ElevateDB does support unicode I'd also
appreciate some feedback from others on how difficult it is migration an app from DBISAM
to ELEVATE.

Thanks.

Marc

marc


ElevateDB  does support unicode. Conversion is the piece of string question. I'd say the primary influence on ease/difficulty is the extent to which you currently use sql, and especially if you heavily use features in DBISAM that didn't make it into ElevateDB.

Roy Lambert

marc


Being my normal nosey self - ONE string field in a database - what's the app?

Roy Lambert

Marc,

<< Does ElevateDB support unicode? >>

Yes, but on a all-Unicode or all-ANSI basis.   It doesn't allow mixing of
the two.

<< I have an application using a DBISAM database, there is one string field
in the database I want to convert to unicode/widestring. So assuming
ElevateDB does support unicode I'd also appreciate some feedback from others
on how difficult it is migration an app from DBISAM to ELEVATE. >>

Just use one of the Unicode versions of the migrators provided with the
Unicode ElevateDB Manager in the Additional Software and Utilities download
here:

http://www.elevatesoft.com/scripts/download.dll?action=downinfo&producttype=edbadd&version=1

and you'll be all set in terms of moving the data across.  You can find out
more information here:

http://www.elevatesoft.com/scripts/manual.dll?action=mantopic&id=edb1&product=d&version=5&category=2&topic=2

All of the Unicode versions of the migrators and EDB manager have "unicode"
at the end of their sub-directory under the main installation directory.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks, I should have made clearer I'm using local tables, not client server - does that
make any difference?

Roy, I've already made the app and database mostly unicode by using blobs where I can,
when I said one string field - there's just one particular field in the database that if I
can convert to unicode will make life much easier

Just so I understand Tim, if I want to use unicode in my local table database I have to
convert all strings fields, not just the one?

Marc,

<< Thanks, I should have made clearer I'm using local tables, not client
server - does that make any difference? >>

Nope, none at all.

<< Just so I understand Tim, if I want to use unicode in my local table
database I have to convert all strings fields, not just the one? >>

Well, you don't actually have to convert anything - the migrator takes care
of that.  However, you will have to change your TStringField objects in your
application to TWideStringField objects, and you will have to use BDS 2006
or higher for complete Unicode support in the TDataSet layer.  I forgot to
mention that last part to you when you initially mentioned that you're using
D5.   BDS 2005 and earlier don't have proper support for WideString CLOB
columns (memo fields in DBISAM), therefore we only support using BDS 2006
and later with the Unicode versions.

--
Tim Young
Elevate Software
www.elevatesoft.com