I faced that trouble a few years ago with forms. I think so it's about hardware problems. Because I don't faced that from a long time. I faced with both of VFP and Foxpro DOS.

The worst thing is, Foxpro doesn't recompile screens if you don't make any change so you can live with these forms. When you faced the truth it's too late to restore from backups. Because all backups are overwrited with these forms.

I know if I used Sourcesafe I can't see that problem, but I can't like Sourcesafe. It makes me slow.

>I know I've heard of this happening before but I don't recall it every happening to me .. or more importantly .. what I can do to solve the problem.
>
>I'm working on a complicated report. There are a few lines of code in the BeforeOpenTables and AfterCloseTables methods. Yesterday my report quit working and I couldn't figure out why it wasn't working. Then I finally realized that the code in those methods is now trashed and garbled and full of funky characters. I fixed up the methods and then continued working on the report. Later in the day, it happened again .. but of course took me a long time to realize that it happened again. Well .. it happened again this morning.
>
>Does anybody recall this bug and what the story is? This is a complicated report and I've been crashing it while running it because of not having other code right .. but that should TOUCH my report definition.