This is along the lines of the infamous "Unknown" datasessions. When users need to go to do packing/indexing, they need exclusive use. The database however seems to be able to be opened exclusively (the check) which leads to the mistaken assumption that the tables will also be able to be opened exclusively. Of course, USE xxx EXCLUSIVE blows up and this is typically due to some private datasession still lingering around. CLOSE TABLES ALL, CLOSE DATABASE sometimes don't seem to work properly. Several forms have comboboxes that have SQL cursors created to populate them. I reread the thread posted by Michelle Cox regarding the "Cannot access the selected table" error message which is also happening here. So, what's needed is a sure fire manner to close out everything from a private datasession.

Steve