Robert,

<< I think this is a bug (Tim will confirm or deny, I'm sure). Unprepare
should put everything back to where it was before the prepare. >>

You're missing the whole point of the KeepTablesOpen property.  If we had
the UnPrepare close the tables, then it would effectively negate the
KeepTablesOpen property altogether.

--
Tim Young
Elevate Software
www.elevatesoft.com

Silven,

<< The table is used twice in the application 1. using the query I showed
you  2. After the query on a second button click, I try to open the table in
exclusive mode, It is at this point that I was getting the error until I set
KeepTablesOpen:= False.  I know it is the query causing the problem because
if I remove the step that calls this function with the query I sent I have
no problem clicking the second button putting the table in exclusive mode
and then emptying.  It is like to query or something is holding the table
for some reason not sure why. >>

Yep, the query will keep the table open in such a case, preventing the
exclusive open.  This is normal.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:AFE73BE8-3226-4E36-B2F3-58DC3A1514E9@news.elevatesoft.com...
>
> You're missing the whole point of the KeepTablesOpen property.

Are you suggesting I should read the manual? You take all the fun out of
programming

Robert

Robert,

<< Are you suggesting I should read the manual? You take all the fun out of
programming >>

Well, it's up to you whether you read the manual.  As for taking the fun out
of programming, just add it to the list.

--
Tim Young
Elevate Software
www.elevatesoft.com