>My company uses VFP but we have a number of lagacy applications in both DOS & Windows FoxPro 2.6 that just can't be converted and/or rewritten for some time. We now operate these on NT Server 4.0. VFP applications run fine. 2.6 applications perform well, but upon exiting out of the application and thus FoxPro, The server will hold onto the FoxPro files (DBFs and sometimes even applications) and show them as open resources (for days, if the resource is not manually closed at the console). This creates the ability to run the app again because the resources it needs are tied up. The DBFs are not used exclusive. Any answers?


I'm not sure why this problem would occur with 2.6 vs VFP apps, but you may want to check out MS KB article #Q129202 on "Opportunistic Locking". According to the article, this behavior can occur with ANY application that uses DBF files.