ElevateDB 2.15 is now available for download.

This release includes a major change to all ElevateDB products: the ability
to mix ANSI and Unicode sessions in the same executable or library. This
includes the ElevateDB Manager, the ElevateDB Server (32-bit and 64-bit),
the ElevateDB PHP Extension, the ElevateDB ODBC Driver (32-bit and 64-bit),
and the ElevateDB .NET Data Provider.

Due to the fact that prior releases often separated the ElevateDB Manager,
ElevateDB Server, and ElevateDB ODBC Driver settings by the type of
executable, this change requires that you run a fix utility called
"edbfixunicode.exe" in order to modify these settings so that the ANSI and
Unicode settings are combined into one location. For more information on
this fix utility and its usage, please review the release notes included
with every product.

If you need help with the fix utility or just have questions about how it
works, please feel free to post your questions here.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> ElevateDB 2.15 is now available for download.
>
....
>
> If you need help with the fix utility or just have questions about
> how it works, please feel free to post your questions here.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com

Hi Tim

No questions.
The download is now at light speed.  
In my case (unicode only) the installer did not detect and uninstall
the prior version so I had to go back and do that myself.

The fix utility did not really work for me either (W7).  The inviting
links did not include a version with the merge parameter - I guess I
should have run it from a cmd prompt.  I ended up just re-creating my
Sessions in the EDBManager.

Malcolm

Hi Tim

Upgraded from 2.13 to 2.15 this morning  and now I get "ElevateDB Error #100 ...(Then encryption password does not match ...) when trying to run  a session against an encrypted database both with my own code and with ElevateDB manager. Reverted my own code to 2.13 and it works again.

Best wishes

Jeff


"Tim Young [Elevate Software]" wrote:

ElevateDB 2.15 is now available for download.

This release includes a major change to all ElevateDB products: the ability
to mix ANSI and Unicode sessions in the same executable or library. This
includes the ElevateDB Manager, the ElevateDB Server (32-bit and 64-bit),
the ElevateDB PHP Extension, the ElevateDB ODBC Driver (32-bit and 64-bit),
and the ElevateDB .NET Data Provider.

Due to the fact that prior releases often separated the ElevateDB Manager,
ElevateDB Server, and ElevateDB ODBC Driver settings by the type of
executable, this change requires that you run a fix utility called
"edbfixunicode.exe" in order to modify these settings so that the ANSI and
Unicode settings are combined into one location. For more information on
this fix utility and its usage, please review the release notes included
with every product.

If you need help with the fix utility or just have questions about how it
works, please feel free to post your questions here.

Tim Young
Elevate Software
www.elevatesoft.com

Malcolm,

<< In my case (unicode only) the installer did not detect and uninstall the
prior version so I had to go back and do that myself. >>

Yes, I forgot to mention that - the names are different now, so the newer
install won't detect an older Unicode-stamped installation.

<< The fix utility did not really work for me either (W7).  The inviting
links did not include a version with the merge parameter - I guess I should
have run it from a cmd prompt. >>

There is no merge parameter, just an overwrite parameter.

Which fix utility did you use ?  You have to use the fix utility that comes
with the ElevateDB Additional Software and Utilities download in order to
fix the ElevateDB Manager sessions information in the edbmgr.ini file.  You
can't use the one that is shipped with the VCL installations - that deals
with the server .ini files separately.  This was done to avoid any
unexpected conversions that weren't intended.

Tim Young
Elevate Software
www.elevatesoft.com

Jeff,

<< Upgraded from 2.13 to 2.15 this morning  and now I get "ElevateDB Error
#100 ...(Then encryption password does not match ...) when trying to run  a
session against an encrypted database both with my own code and with
ElevateDB manager. Reverted my own code to 2.13 and it works again. >>

What version of Delphi are you using ?  By default, the
TEDBEngine.CharacterSet, and subsequently, the TEDBSession.CharacterSet
property are set according to the compiler in use.  So, if you're using
Delphi XE and trying to access ANSI databases, then you're going to need to
change the TEDBEngine.CharacterSet property to csAnsi manually in your
application project.

Tim Young
Elevate Software
www.elevatesoft.com

No problem Tim

I installed the VCL first and tested it .. uh, oh.  
Then used the VCL version of the fix - inappropriate.

Sorry, mentioned the word 'merge' inexactly since that was the
intention.
(But I did not use any parameter)

Then I installed the 'ADD'.
Anyway, all sorted easily enough.  
Next time it will be a doddle.

Malcolm

Hi Tim

Thanks for getting back to me.

We're using Delphi 2010 but it's the upgrade from ElevateDB 2.13 to 2.15 and the manager from 2.12 to 2.15 that seems to cause the problem. That's the only change here. As soon as I re-installed the old versions of ElevateDB and the manager it all worked again without any other change.

Best wishes

Jeff


"Tim Young [Elevate Software]" wrote:

Jeff,

<< Upgraded from 2.13 to 2.15 this morning  and now I get "ElevateDB Error
#100 ...(Then encryption password does not match ...) when trying to run  a
session against an encrypted database both with my own code and with
ElevateDB manager. Reverted my own code to 2.13 and it works again. >>

What version of Delphi are you using ?  By default, the
TEDBEngine.CharacterSet, and subsequently, the TEDBSession.CharacterSet
property are set according to the compiler in use.  So, if you're using
Delphi XE and trying to access ANSI databases, then you're going to need to
change the TEDBEngine.CharacterSet property to csAnsi manually in your
application project.

Tim Young
Elevate Software
www.elevatesoft.com
Jeff Gallant
Technical Manager
Computing for Labour
United Kingdom

Jeff,

<< We're using Delphi 2010 but it's the upgrade from ElevateDB 2.13 to 2.15
and the manager from 2.12 to 2.15 that seems to cause the problem. That's
the only change here. As soon as I re-installed the old versions of
ElevateDB and the manager it all worked again without any other change. >>

Yes, but did you read the release notes and run the Unicode fix utility,
etc. ?  This is *not* a seamless new release, it requires you to make some
minor changes in order to accommodate the merging of the ANSI and Unicode
versions of ElevateDB.  If you're using ElevateDB 2010 and you're using ANSI
databases, then you *must* change the TEDBEngine.CharacterSet property to
csAnsi in your application or you will get these type of errors.  Likewise,
if you don't run the Unicode fix utility that is provided with the ElevateDB
Additional Software and Utilities download, your ElevateDB Manager sessions
will *not* get changed so that they are set as ANSI sessions instead of
Unicode sessions, which is now the default for the ElevateDB Manager.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

Good news - it's all working now. Thanks for your help.

I did read the release notes but, like most users, I didn't read them fully. I did run the utility but missed the instructions on how to run it because they are separated from the bit that tells you to run it in the first placer So I didn't run it as admin nor with a parameter.

However, having run it, I still couldn't access my database in Manager. I had to explicitly edit the session to change the character set. The bit regarding the our own code worked fine. I changed the engine property and all is fine now.

So, again, thanks for your help.

Best wishes

Jeff

Jeff Gallant
Technical Manager
Computing for Labour
UK

PS I see on the news you've had some awful weather over there. Hope you and your colleagues are not too badly affected.


"Tim Young [Elevate Software]" wrote:

Jeff,

<< We're using Delphi 2010 but it's the upgrade from ElevateDB 2.13 to 2.15
and the manager from 2.12 to 2.15 that seems to cause the problem. That's
the only change here. As soon as I re-installed the old versions of
ElevateDB and the manager it all worked again without any other change. >>

Yes, but did you read the release notes and run the Unicode fix utility,
etc. ?  This is *not* a seamless new release, it requires you to make some
minor changes in order to accommodate the merging of the ANSI and Unicode
versions of ElevateDB.  If you're using ElevateDB 2010 and you're using ANSI
databases, then you *must* change the TEDBEngine.CharacterSet property to
csAnsi in your application or you will get these type of errors.  Likewise,
if you don't run the Unicode fix utility that is provided with the ElevateDB
Additional Software and Utilities download, your ElevateDB Manager sessions
will *not* get changed so that they are set as ANSI sessions instead of
Unicode sessions, which is now the default for the ElevateDB Manager.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Jeff,

<< Good news - it's all working now. Thanks for your help. >>

Good to hear.

<< However, having run it, I still couldn't access my database in Manager. I
had to explicitly edit the session to change the character set. The bit
regarding the our own code worked fine. I changed the engine property and
all is fine now. >>

You might be falling into the "logic hole" that exists when both the Unicode
and ANSI settings files exist on the machine.  In such a case, EDB will not
update the character set for sessions that exist in the ANSI settings file,
but not in the Unicode settings file.  I've fixed this, and the fix will be
in the next build 2.

<< PS I see on the news you've had some awful weather over there. Hope you
and your colleagues are not too badly affected. >>

Nah, not too bad, thanks.  Just staying indoors and keeping warm.

Tim Young
Elevate Software
www.elevatesoft.com