Hi

I am trying to migrate my application from using BDE/Paradox to ElevateDB.  I have found
that the exclusive property behaves differently for each of the two table components.
TTable.Exclusive can still be set to true if the table is already open inside the
application, but TEDBTable.Exclusive cannot.

Please can you confirm that this is correct? Also, is there another way of ensuring that
TEDBTable.Exclusive = True is successfully executed, without having to check whether all
tables/queries in the application using that table are closed?

Thanks

Ravinder,

<< I am trying to migrate my application from using BDE/Paradox to
ElevateDB.  I have found that the exclusive property behaves differently for
each of the two table components.  TTable.Exclusive can still be set to true
if the table is already open inside the application, but TEDBTable.Exclusive
cannot.

Please can you confirm that this is correct? >>

Yes, this is correct.  The BDE allows multiple table components within the
same session to all have exclusive access to the same physical table,
whereas EDB requires that one, and only one, table component have exclusive
access to a given physical table.

<< Also, is there another way of ensuring that TEDBTable.Exclusive = True is
successfully executed, without having to check whether all tables/queries in
the application using that table are closed? >>

I'm afraid not - you have to make sure that no other table components or
sessions have the table open in a shared or exclusive state.

--
Tim Young
Elevate Software
www.elevatesoft.com