Enviroment:  ElevateDB 2.03 Build 21 and Delphi 7
Error encountered:  ElevateDB Error #506 Cannot lock the session manager
(ID: 1)

We are in transition from dbIsam to ElevateDB, and I built a routine that
would summarize daily transactions in dbIsam and insert the result in
ElevateDB tables.  I thought as in my previous post above error (#506)  has
been solved with my update to Elevatedb 2.03 build 21.

Given an active myDBISamQuery, I call the routine below.  DBIsamQuery result
set with less than 700 records works fine.  If the result set is greater
than 700, I encounter above error.  I tried putting delays and flush buffers
after each 100 record appends/inserts and it works.   This is on an
application running on a remote location.

Also, I tried running the application in the server computer without the
flush buffers and delays, and it work without errors.

Is there some command that we can use to check whether ElevateDB server is
ready for the next insert/append, issued from a remote computer?

Thanks,
George Patena


Here's the routine that I call with each DBISamQuery result set:

myEdbQuery.SQL.Clear;
myEdbQuery.SQL.Add('insert into mydb.DailySummary ');
myEdbQuery.SQL.Add('(a, b, c, d, e, f, g)');
myEdbQuery.SQL.Add('Values (:a, :b, :c, :d, :e, :f, :g)');
while not myDBISamQuery.EOF do begin
         myEdbQuery.ParamByName('a').AsString:=myDbisamQuery.Fields[0].AsString;
         myEdbQuery.ParamByName('b').AsString:=myDbisamQuery.Fields[1].AsString;
         myEdbQuery.ParamByName('c').AsInteger:=myDbisamQuery.Fields[2].AsInteger;
         myEdbQuery.ParamByName('d').AsDate:=myDbisamQuery.Fields[3].AsDateTime;
         myEdbQuery.ParamByName('e').AsString:=myDbisamQuery.Fields[4].AsString;
         myEdbQuery.ParamByName('f').AsInteger:=myDbisamQuery.Fields[5].AsInteger;
         myEdbQuery.ParamByName('g').AsCurrency:=myDbisamQuery.Fields[6].AsCurrency;
         myEdbQuery.Prepare;
         try
           myEdbQuery.ExecSQL;
         except
           showmessage('Error ini: ['+myEdbQuery.SQL.Text)
               +']    ['+mydbIsam.SQL.text+'['   ;
           break;
         end;//try except
         myDbiSamQuery.Next;
end; //while

George,

<< We are in transition from dbIsam to ElevateDB, and I built a routine that
would summarize daily transactions in dbIsam and insert the result in
ElevateDB tables.  I thought as in my previous post above error (#506)  has
been solved with my update to Elevatedb 2.03 build 21.

Given an active myDBISamQuery, I call the routine below.  DBIsamQuery result
set with less than 700 records works fine.  If the result set is greater
than 700, I encounter above error.  I tried putting delays and flush buffers
after each 100 record appends/inserts and it works.   This is on an
application running on a remote location. >>

Also, I tried running the application in the server computer without the
flush buffers and delays, and it work without errors. >>

Can you send me a sample project that reproduces the issue over the network
?   I can run it here with a "network slowdown" utility and see if I can
reproduce the issue.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

George,

Just to confirm - you're not running the application in the IDE when getting
this exception, are you ?  It's possible to see this exeption when running
in the IDE, but it is trapped by EDB and handled internally.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Yes,  I was running in the IDE when I get the error!  I tried running
outside the IDE and the inserts are super fast!   Wow.  There are plenty of
times I want to go back to dbISAM when I am stuck with some EDB issues, but
the appeal and goodies of EDB keeps me going .

Thanks  for knowing solutions to (almost) everything,
George




"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:D57C3906-A9C8-476D-9BF4-D0C0ED23CACF@news.elevatesoft.com...
> George,
>
> Just to confirm - you're not running the application in the IDE when
> getting this exception, are you ?  It's possible to see this exeption when
> running in the IDE, but it is trapped by EDB and handled internally.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com

George,

<< Yes,  I was running in the IDE when I get the error!  I tried running
outside the IDE and the inserts are super fast!   Wow.  There are plenty of
times I want to go back to dbISAM when I am stuck with some EDB issues, but
the appeal and goodies of EDB keeps me going . >>

Thanks, I'm glad that the problem is what I thought it was.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim:
Been encountering this error too and glad I found this thread, now I know not to be concerned about the error.

LOL, we are converting Btrieve to ElevateDB and comparing reporting times. The only time EDB loses is when the SQL is not written correctly or through iteration, the SQL is executed hundreds and sometimes thousands of times.

Just a great product. Keep it up!

Thank you,


Daniel

Daniel,

<< Been encountering this error too and glad I found this thread, now I know
not to be concerned about the error. >>

Just to let everyone know: I've changed this around so an exception isn't
reported anymore, so you won't get any confusing exceptions in the IDE
anymore.  This will be in 2.04 B5.

<< LOL, we are converting Btrieve to ElevateDB and comparing reporting
times. The only time EDB loses is when the SQL is not written correctly or
through iteration, the SQL is executed hundreds and sometimes thousands of
times. >>

Fantastic.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Is this 506 issue supposedly resolved or did I miss a later post on another thread acknowledging that it still appears?  I get this using D6 all the time with the latest build (2.05 B10) when I am in the IDE , so I know firsthand that it was not resolved, at least as far as D6 is concerned.  

Regards

Mike Feran





"Tim Young [Elevate Software]" wrote:

Daniel,

<< Been encountering this error too and glad I found this thread, now I know
not to be concerned about the error. >>

Just to let everyone know: I've changed this around so an exception isn't
reported anymore, so you won't get any confusing exceptions in the IDE
anymore.  This will be in 2.04 B5.

<< LOL, we are converting Btrieve to ElevateDB and comparing reporting
times. The only time EDB loses is when the SQL is not written correctly or
through iteration, the SQL is executed hundreds and sometimes thousands of
times. >>

Fantastic.

--
Tim Young
Elevate Software
www.elevatesoft.com

<<<mferan wrote:

Hi Tim,

Is this 506 issue supposedly resolved or did I miss a later post on another thread acknowledging that it still appears?  I get this using D6 all the time with the latest build (2.05 B10) when I am in the IDE , so I know firsthand that it was not resolved, at least as far as D6 is concerned.  

Regards

Mike Feran
>>>>

Tim:

I've run into a a few times with 2.05 B10 as well.  I have not been able to reliably duplicate it yet though.  I can't remember if it happened in the IDE but I do know that it has happened a couple times when the IDE was open but I was running the program as a compiled .exe (ie: outside the IDE).

Wish I had more information to pass along to you.

Dale




"Tim Young [Elevate Software]" wrote:

Daniel,

<< Been encountering this error too and glad I found this thread, now I know
not to be concerned about the error. >>

Just to let everyone know: I've changed this around so an exception isn't
reported anymore, so you won't get any confusing exceptions in the IDE
anymore.  This will be in 2.04 B5.

<< LOL, we are converting Btrieve to ElevateDB and comparing reporting
times. The only time EDB loses is when the SQL is not written correctly or
through iteration, the SQL is executed hundreds and sometimes thousands of
times. >>

Fantastic.

--
Tim Young
Elevate Software
www.elevatesoft.com

I spoke to Tim about this today and he gave me some tips on where to look for the cause.  If I get it figured out I will post it here.

Dale