I would expect the MSC to repair only what it can report. if you already know the name of the offending method (for example, you record the crashing sequence and play back in slow motion) you might be able to extract, save and replace the code with METHOD SET CODE.
for example, you might be able to take advantage of the On Host Database event to do that without going to Design, or even do so directly by pasting a one-liner in the debugger's expression pane. 2017/02/08 17:45、Douglas Cryer <[email protected]<mailto:[email protected]>> のメール： I did this for verifying and repairing both of which reported the structure was good. Am I missing something? Is there some way of looking deeper at the structure in MSC? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
