>I know the answer must be yes. But I have a situation where system maintenance is to be performed. A killit.txt file gets written to the server. The app has a timer that looks for killit.txt. When it sees killit.txt the app executes the cleanup code. The cleanup code does the traditional, and it does a CLOSE ALL RELEASE ALL, but it does not do any unlocks. The person who needs to do the system maintenance then tries to open the files exclusive, but many times they can not. Noone else is in the app, but the files can not be opened exclusive. Either someone who got kicked out still has a file opened or a lock on the file, or possibly the person who kicked everyone off is preventing themselve from open exclusive. The killer does a CLOSE DATA, and then opens the needed files exclusive.
>
>Any ideas?
>
>Brenda

The problem may be caused by other users not properly shutting down the application before turning off their computer. Client system lockups / crashes may also leave tables open on the server.