>I'm thinking along the same lines. It's the only thing that makes any sense. I'd wager that the reserved field holds the size and/or offset of the method into the methods memo field, and that, internally, VFP uses that to calculate what to display. Since internally, the memo field has the PROCEDURE/ENDPROC pair, it must use the values to determine what to display in the window in a quick and efficient method.

Not there - the Reserved3 holds the status (property/method), and whether it exists in the parent class or not (first byte of each line - a blank, asterisk or exclamation mark, I forgot which means what). Then there comes the name, and the description after a semicolon (if description exists), and a CR to end the line. No binaries there. It's most probably in the objcode memo.

>I was unnecessarily nervous about this, because this is the class that's the "OLE Automation Server from Hell". Be a real pain to have to re-construct it. Very complex. Calculates yarn weight for carpet based on the denier and step patterns of the needle bars. If I lost this, I'd take me out back and shoot me.:-)

You could still copy all the methods from the memo and paste them one by one into the methods of a new class, adding their names in a regular manner (Class/New Method) like a good schoolboy, or you could still hack the Reserved3 :)

So while the reasons of this remain a mystery, the cure is simple...