>>>Do you get any error reported if you open the .FRX/.FRT as a table? Maybe it has to do with more-advanced table error checking in VFP9.
>>
>>I can open it as a table. The weird deal is that it is not always the same FRT file that this gets reported on. I also see the same problem issuing the BUILD commands from the Command window. I can even MODIFY REPORT and save without problems. I am starting to think its a failure to release a file handle issue.
>
>- Does the problem persist across a reboot?

Yep, and even after deleting the FOXUSER files before the reboot/restart of VFP

>- Are there any issues if you open the .PJX as a table?

Nope

>- Do you have anything happening in a ProjectHook?

I do, but nothing that has anything to do with report files.

The other bizarre thing is this exact same project is on another (slower) computer running Win2k Pro and I do not have this problem at all. I am transferring this entire project to someone else whose computer is running WinXP Pro. The directory tree structure is slightly different, but we fixed all the mapping issues, set the new project home folder etc., so we are not getting relative directory errors or any other compile errors.

I can also issue COMPILE REPORT *.FRX from the command window numerous times in a row and get NO corruption errors. Only when I try to build the app. Gotta be a memory garbage cleanup thang.