FYI, my application uses CO400 and Paradox (to store the data
locally).  We move the data using TBatchMove from the AS/400 and store
in local Paradox tables.  Each table is uniquely named so that
shouldn't be the problem (this has been verified as well).  Once the
data has been downloaded, we open the appropriate table with a TQuery.

For the function that's blowing up...I downloaded the data at
application startup.  My lookups against this Paradox table are via a
Parametized query (which I know works).  I've got exception handling
everywhere trying to trap the offending line but no luck.

Anyone else seen this error?  How'd you get around it?

TIA,

Charles

There seems to be a bug in the VCL which causes this error. See my
post 'Serious BUG in VCL (dbtables.pas)' earlier or contact me
directly: mduerig at eye.ch (replace at with @ and remove spaces)

Michael

Thoughts?

Charles

mduerig at eye.ch (Michael R. Duerig) wrote in message
<6ps7as$mk...@forums.borland.com>...

If you use additional sessions in you applications I can give some
hints which might help you:

If not necessary don't use additional sessions. It's only necessary if
you access your databases from different threads.

If you have to use sessions I found two workarounds which worked for
me:
1. Don't prepare your query. Instead of

if not MyQuery.prepared then
  MyQuery.prepare;
MyQuery.open;

just use MyQuery.open The VCL takes care about preparing anyway so
performance shouldn't be a matter.
The reason for this is that if you explicitly prepare the query the
VCL sometimes executes some BDE API calls in the context of the wrong
session on consecutive calls to MyQuery.open.

2. Explicitly set the correct session:

if not MyQuery.prepared then
  MyQuery.prepare;
DbiSetCurrSession(MySession.Handle);
MyQuery.open

Good luck

Michael

I have read (? Delphi Help or elsewhere) that an application should call
BDE function DbiInit only once -- which Delphi components do
automatically, user is not supposed to call this function. May be "some
one" in your app is calling this function without telling you!

The error you mention is generated if a second call is made to the above
BDE function.
Following is  from x:\Delphi_n\Doc\BDE.int
-----------------
ErrCode_ReEntered = 7; {System has been illegally re-entered}

Thanks

jay mavi

procedure SafeOpen(TDS:TDataset);
begin
    EnterCriticalSection(CritSec);
    try
        if TDataSet is TTable then
            Sessions.OpenSession((TDS as TTable).SessionName);
        if TDataSet is TQuery then
            Sessions.OpenSession((TDS as TQuery).SessionName);
        TDS.Open;
    finally
        LeaveCriticalSection(CritSec);
    end;
end;

...

initialization
    InitializeCriticalSection(CritSec);
end;

Thank you Michael for your succesful debugging on this and for your warning!
Applying (roughly) the above fix on my code helped a lot.

--
Florin Vancea (fvancea.ns...@texnet.ro)
(please remove nspam from return mail address)

Hello Florin,

Nice to 'meet' you again!
Last weekend I got my copy of D4 and look, Inprise fixed this bug!
First they ensure now that TBDECallback instances are created and
freed in the context of the correct session and 2nd they removed the
registration of cbCancelquery callbacks for TQuery. As a consequence
the event TQuery.OnServerYield has been silently removed.

Michael

On Tue, 4 Aug 1998 14:01:54 +0300, "Florin Vancea"

Best regards, Florin.