Tim,
I registered ElevateDB a few months ago and just started using it this week (long hiatus since DBIsam 3.x - so expect some more questions soon).

I downloaded and installed the latest version (2.01 build 4 --> shows in EDBSession properties) from *** customer area *** BEING CAREFUL NOT
TO DOWNLOAD FROM TRIAL AREA (have done that before).

My Problem: I can NOT change the LicensedSessions property - it reverts to 2.

What am I missing?

Thanks

Jay

Jay


Where are you trying to alter this? In the server I would guess. For me in 2.01b4 that defaults to 6.

What happens if you drop an engine on a form - do you get 4096 licensed sessions?

Roy Lambert [Team Elevate]

<<  Roy Lambert <roy.lambert@skynet.co.uk> wrote:

Jay


Where are you trying to alter this? In the server I would guess. For me in 2.01b4 that defaults to 6.

What happens if you drop an engine on a form - do you get 4096 licensed sessions?

Roy Lambert [Team Elevate]   >>

=============================

Using Delphi RAD Studio 2007 (Win 32) on Windows VISTA Ultimate - in case that matters.

I never changed the EDBEngine.EngineType property (its on a DataModule, it defaulted to: etClient and LicensedSession = 2). Everything else
works OK for a typical DB application scenario: Engine --> Session --> Database --> Dataset --> DBGrid. Just could NOT change:
LicensedSession.

After Roy's message, I changed the EngineType property to etServer which automatically changed the LicensedSessions to 6. Changing
EngineType back to etClient, kept the "6" in LicensedSessions and NOW IT ALLOWS ME TO CHANGE LicensedSessions to a larger number.

This is weird behavior - May be Tim should look at it or at least inform the unsuspecting. Now, who would have guessed to do that - just glad it
works

Thanks Roy.

Jay

Jay


From that description you probably forgot to sacrifice a black chicken before dropping the component onto a datamodule

Roy Lambert

Jay,

<< After Roy's message, I changed the EngineType property to etServer which
automatically changed the LicensedSessions to 6. Changing EngineType back to
etClient, kept the "6" in LicensedSessions and NOW IT ALLOWS ME TO CHANGE
LicensedSessions to a larger number. >>

If the licenses were reverting to 2 at design-time, then that indicates that
you were using an older version of EDB for the design-time package.  The
newer versions of EDB use a limit of 3 for the trial versions:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=1.08&type=f&incident=2563

--
Tim Young
Elevate Software
www.elevatesoft.com

<< "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Jay,

<< After Roy's message, I changed the EngineType property to etServer which
automatically changed the LicensedSessions to 6. Changing EngineType back to
etClient, kept the "6" in LicensedSessions and NOW IT ALLOWS ME TO CHANGE
LicensedSessions to a larger number. >>

If the licenses were reverting to 2 at design-time, then that indicates that
you were using an older version of EDB for the design-time package.  The
newer versions of EDB use a limit of 3 for the trial versions:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=1.08&type=f&incident=2563

--
Tim Young
Elevate Software
www.elevatesoft.com  >>
===============================

Tim,

It is registered version (now allowing me to set LicensedSessions to 4096 or whatever) and Version property in Object Inspector shows: 2.01 build
4. As indicated in my original message - I could NOT change the LicensedSessions property (it reverted to 2 when changed to a larger number).

I am sticking with Roy's Black Chicken theory - I may even quit programming and start a "Black Chicken Farm" to help other programmers !

Jay

Jay,

<< It is registered version (now allowing me to set LicensedSessions to 4096
or whatever) and Version property in Object Inspector shows: 2.01 build 4.
As indicated in my original message - I could NOT change the
LicensedSessions property (it reverted to 2 when changed to a larger
number). >>

Do you have any components that use EDB installed in packages at design-time
?  That, or possibly multiple projects being present in the project manager
could possibly cause confusing issues like this.

--
Tim Young
Elevate Software
www.elevatesoft.com