At 13:05 24.07.2009, Clyde England wrote: >Shouldn't SQLiteSpy release this folder lock when you close the database in >which it resides? Yes and no. What happens here is that when SQLiteSpy creates / opens a database file via an open / save file dialog, it employs the GetSaveFileName / GetOpenFileName Windows API functions. Unless otherwise specified, those functions change the application's current working directory to the one selected last. As a result, the next open / save dialog will start right there without any further program intervention. Unfortunately, this nice feature also locks the current directory as a negative side effect, something I noticed with other applications as well. Directory locking can be avoided by passing the OFN_NOCHANGEDIR option. Unfortunately, this also suppress any working dir changes so the next file open will not automatically remember where the last one left off. Achieving both ends would require to store the working dir as an SQLiteSpy option. As I see it, the directory locking is not a serious problem but a small inconvenience only. Anyway, I kept note of the issue to work on it when I next find some time. Thanks for the detailed report, Ralf _______________________________________________ Delphi Inspiration mailing list yunqa@xxxxxxxxxxxxx //www.freelists.org/list/yunqa