Hello Tore.

I tried again to do those modifications the next day and everything went ok. So now I have doubts. Perhaps I had two sessions opened. Not sure though. Anyway the important thing is that it's working now. Thanks for your feedback.

>If you have more than one VFP session open, you must be careful NOT to open the same scx or vcx more than once, or you may end up with an empty or screwed up vcx or scx. Maybe this also applies to reports.
>
>>>>I wanted to modify the code in an init method of a report.
>>>>
>>>>I added new code and saved the report. When I returned to look at the init code everything was messed up.
>>>>
>>>>Code looked like it was encypted.
>>>>
>>>>I returned to the original version (At least I do back-ups) and did the same modifications. Once again I ended up with an encrypted version.
>>>>
>>>>Anyone have a clue on this one?
>>>
>>>I have report designer bugs all the time. There are two different ones. The fubar code in report DE as you report, and another one that tells you "File Not Open" when trying to save a report.
>>>
>>>To get the File Not Open bug open two reports at the same time and copy code from one to the other then save both reports using Ctrl+W. It's so bad for me that if I have to copy code from one report to another I open first report, copy code, close Foxpro. reopen foxpro. open second report. paste in code.
>>>
>>>I also get corrupt code in my report DE at least once a week. It's so prevalent that I automatically copy and paste code into notepad before closing report, then reopen the report to see if it got FUBAR'd.
>>
>>Thanks for that info Brandon. I'll be waiting to see what others have to say. But I already begun putting that code elsewhere. That should be the solution.