>>>>>>Perhaps someone can help me. I am not using anykind of "code source" software that would make these changes.
>>>>>>
>>>>>>Today I have noticed that I can make a change to a Form's Method, save it, run the program and the changes are not reflected in the code. When I open the form (sometimes but not all the time) the code is lost and reverts back to what was there to begin with. At other times the changes stick.
>>>>>>
>>>>>>A time or two, I have been able to make changes,save them, run the program and the changes were reflected in the running program. Then when I re-opened the form the changes were lost and the prior code was there.
>>>>>>
>>>>>>Any suggestions? Could this be a corrupt foxuser file or something? Perhaps I need to pack something (a project or whatever).
>>>>>>
>>>>>>Help is appreciated and I need it quickly....:)
>>>>>>
>>>>>>Mel
>>>>>
>>>>>Try doing a
>>>>>COMPILE FORM myform.scx
>>>>>..and if there are any .vcx's that are used...do this
>>>>>COMPILE CLASSLIB *.VCX
>>>>>
>>>>>It could be an issue with the timestamps on the files and that should take care of it....
>>>>
>>>>Doesn't compiling the project into a EXE do this? I am running the form that I am experiencing this in from a compiled project - and its EXE.
>>>>
>>>>Any additional thoughts to help me understand this are appreciated.
>>>
>>>I would compile them like this first:
>>>COMPILE FORM *.SCX
>>>COMPILE CLASSLIB *.VCX
>>>...then compile the .exe
>>>
>>>If the timestamps are jacked up, compiling the .exe may not actually compile everything. I've actually had this happen to me before because I got some files from another developer that was in a different timezone. There are other things that can cause it to happen I'm sure - but that is what happened to me. Took me a bit to figure out that was what was happening too. Anyway like I said try compiling the stuff individually, THEN compile the .exe. I think if the .sct has a timestamp after the .scx, then the .scx is not recompiled when you do a build .exe - even if you have selected to recompile all files. Kinda a bug if ya ask me.
>>
>>
>>Thanks Victor, sounds like a good plan.
>>
>>Just for clarification, are you saying that if I COMPLIE FORM for the problem Form, then that will take care of it - and I don't have to do this every time that I am compiling into a EXE? In otherwords the COMPLIE FORM one time should take care of it even as I continue to make additional changes to the Form?
>
>I would think so, but of course that depends on how the problem happened to begin with. In my case I just had to do it one time - until I got another set of files from my guy in another timezone. I would strongly recommend compiling all you .prg , classlibs and forms first using
>
>COMPILE *.PRG
>COMPILE CLASSLIB *.VCX
>COMPILE FORM *.SCX
>
>..and do them in that order too! - then compile your .exe and HOPEFULLY that will fix your problem.

Thank you... will do.

Mel