I agree with Olaf Doschke and Fabio Lunardon on the correlation between the METHODS and OBJCODE fields. I have seen instances where the method code "is all junk" -- code is split over a number of different methods; a quick COMPILE FORM (or CLASSLIB) fixes the problem. There is some protection in the methods for not using the PROCEDURE ENDPROC FUNCTION or ENDFUNC keywords (amoung others) in the editor which would mess the code up internally, but these keywords appear in the METHODS field. I have successfully copied blocks of methods into a VCX or SCX by appending the text to the METHODS field and then adding the method names manually in the RESERVED3 field followed by a COMPILE FORM command.

What is also interesting, is that you can blank out the METHODS field after compilation and use it in a project. The form/class still works (all methods are being executed). You can use ReFox to decompile the OBJCODE field and see the method text.