>>>When VFP asserts a SELECT-SQL statement with a table, it leaves the table open even if it was not already open. However, it does not put you in the workarea (or tell you the workarea) in which the table was opened. If you do SELECT from two tables with the same file name (different folders), then you end up with one alias named according to file name, and the other alias name is made up by VFP (an ABC letter). Lets assume that both of those tables need to be opened/accessed at the same time. The question then, when it's time for cleanup, is how to find those "Left-hanging-around" tables so you can explicitly close them. Any suggestions? Thanks very much.
>>
>>Seldomly you need to find them. Why would you bother with closing them provided you use private data sessions. Or you could prevent them being opened with VFP supplied aliases opening yourself.
>>Cetin
>
>That's actually what I've been doing:

>USE (cBlahTable) noupdate shared alias DataSource in 0
>Select blah blah from DataSource
>use in DataSource

Mark,
I don't really see a need to do it but there is another way too (instead of tracking what you opened):
SPT, CursorAdapter with OLEDB/ODBC. They don't leave tables behind open.
Cetin