Try setting the desktop date to the date in the error message, and then run the program. It may be one of those BATCH locks thats requires some kind of posting activity each day. Or, it may a "programmed" error that locks the system to notify that someone opened the file outside the application environment (eg from foxpro, and not the app). There may (must) be some file (a DBF) that records dates the files were last opened. If you run the program, you know for sure that it opend that file to check the dates before it opened application files. Run the program, let the error happen, and then cruise through the dbf directories to localize a date/time stamp that reconciles with your last attempt to run the program. "Use" those files. They probably are small with ver6y few records. Check the fields to see if they have dates.

ANother method to isolate the "date check" file would be to ren all the dbfs to *.FOO. Then as the app runs, the runtime error manager should report that it could not locate a particular DBF (and show the name). Just go through each error break, rename the FOO to DBF and see if it has those date check fields you are looking for.

I imagine there are some SYS commands that may echo the line of code that is executing to a window or file, but I'm not sure.

>You are probably right, and in all likelyhood I have no recourse. I don't know if Refox is legally applicable or not - maybe I can check into that angle.
>
>Thanks for your help.
>
>Kim