Hi there

I thought I had installed a unicode enabled version of ElevateDB std, but it appears (now that I am attempting to implement unicode) that that is not the case.

I would like some direction in how to implement unicode capability for the database.

Can I use EDB std - unicode is a compile time conditional, yet I do not have the source code?

Once I have EDB recompiled to handle unicode, what is the best practice for migrating the non-unicode DB to unicode-capable DB, given I cannot simply reuse it? If I reverse engineer non-unicode version, can I then create a unicode version using the generated SQL?

Your assistance would be greatly appreciated.

Aaron

Aaron


I would suggest that you download the unicode version for whatever your development environment is but your post seems to say that you did. If you have downloaded the unicode version but your environment doesn't support unicode that could give you a problem.

Can you post some more info about version.

Roy Lambert [Team Elevate]

I consider myself relatively intelligent but for the life of me cannot find a download page that will let me download the product I bought in a unicode version.

I located an email advertising Build 3 of Version 2.05 of ElevateDB. It recommends going to the downloads page. When I go there, the following list of downloads for EDB VCL STD are all I can see:


EDB-VCL-STD - ElevateDB VCL Standard
Includes the standard ElevateDB client engine in VCL component form with local and remote capabilities. Also included is a special 5-session version of the ElevateDB Server for small installations and testing purposes. Does not include any source code.

This product can be used with Borland Delphi, Developer Studio, or C++Builder, and CodeGear RAD Studio.

Download ElevateDB VCL-STD - Version 1.09 Build 4
Download ElevateDB VCL-STD - Version 1.08 Build 1
Download ElevateDB VCL-STD - Version 1.07 Build 3
Download ElevateDB VCL-STD - Version 1.06 Build 1

So um yeah I clicked on one of those products then changed the URL parameters to arrive at my desired destination.

1. not sure if this is a secuirty flaw
2. think there may be something wrong with the downloads page?

I have a headache and it's late, it's also possible I am at fault here, happy to be enlightened.

So back to my original query:

If I do a reverse engineer of the ANSI DB, change all the collations to UNI_<etc etc> and run that using the unicode DB manager, I should be right to go yes?

Appreciate any pointers / advice in migrating an ANSI EDB database to unicode.

Thanks
Aaron

Aaron


That reads as though your subscription might not be up to date.

Roy Lambert [Team Elevate]

<<Roy Lambert wrote:

Aaron

That reads as though your subscription might not be up to date.

Roy Lambert [Team Elevate]>>

I purchased the upgrade from DBISAM to ElevateDB April 28, 2010.
I have EngineVersion 2.03 Build 12 installed, which was announced on April 27, 2010.

Whether my subscription is up to date or not, I should still be able to access the product I purchased, I would have thought.

It is also irrelevant to my question, which pertains to migrating an ANSI DB to UNICODE.

Aaron,

<< So um yeah I clicked on one of those products then changed the URL
parameters to arrive at my desired destination. >>

Yes, it's a problem with the web server, and it has been fixed.  It's not a
general security flaw - it was specific to your customer information, and
the main problem was that your order did not have a support plan attached
when you purchased the upgrade to EDB from DBISAM.

You're all set now.

--
Tim Young
Elevate Software
www.elevatesoft.com

<<"Tim Young [Elevate Software]" wrote:

Aaron,

<< So um yeah I clicked on one of those products then changed the URL
parameters to arrive at my desired destination. >>

Yes, it's a problem with the web server, and it has been fixed.  It's not a
general security flaw - it was specific to your customer information, and
the main problem was that your order did not have a support plan attached
when you purchased the upgrade to EDB from DBISAM.

You're all set now.
>>


Thanks Tim, much relieved.

I have 2.03 ANSI installed and installed 2.05 UNICODE over the top. It failed dismally when I started up Delphi again, so I uninstalled UNICODE version.

Can you please point me to help in migrating what is now quite a large EDB ANSI project to UNICODE?

Thanks
Aaron