>>>What about the Project window, is it open? If the database is referenced in the project, it won't "really" close unless you close the project too.
>>>
>>
>>Nope, that's not it. PM is closed and I'm running the app from the command window right now, still testing.
>>
>
>Any table-buffered views with pending changes? If you issue a SET command after all the "CLOSE" commands, you should see if there is one of those (if that was the case, TABLEREVERT(.T.) would be useful)

Nope, that's not it either, :-). First, there are no views with pending changes open in the datasession and second, issuing the close tables does close all of the databases tables as I've examined this from the data session window.

The problem that I am specifically having is with Stonefield database toolkit's method of opening a database, when called via a hook in Visual MaxFrame similar to this;

lcDataDirectory = "c:\myapp\mydatadir1"
lcDBC = lcDataDirectory + "\master"

oLib.oDBCSvc.OpenData(lcDBC,.t.,.f.)

In my app I'm using the same database name in different data subdirectories, and even if I pass an explicit path to SDT for the database I want to open as a parameter, which is supported btw, the dbused() function as used in the SDT code causes the wrong database to open by just reopening the prior selected database with the same name. If I could get the dbused() function to return .f., I could proceed. If SDT would not use the dbused() function and just open the database in the passed parameter, I could proceed. Given that those are my 2 options right now, you can see why I need the dbused function to return a .f., :-) I'm really stuck on this issue and will have to create a workaround if I can't get it to work this way. :-(