>>Does your builder work on a PRG or a visual class? I would think a PRG would be easier. If you look at the actual code, the methods start with PROCEDURE some_name and ENDPROC. Your procedure to Remove a method would have to look for PROCEDURE and its corresponding ENDPROC.
>
>>Of course doing anything like this, I would include a procedure at the beginning of my builder to make a backup copy first.
>
>>To get a better answer, more info about the builder and class would be helpful.
>
>The builder would need to add methods on a visual class. The builder would not need to add any code into the methods during building. The methods would be used later.
>
I do not see any reason why you could not do this. Practice on a dummy VCX. Create a new VCX with only 1 class in it [I based mine on a form]. Open the VCX as a table, go to the record this is the form class. Custom methods are stored in Reserved3 field. Populate its contents with --
*MyMethod plus a return. Or you can do something like
Replace Reserved3 with "*MyMethod1" + chr(13) + "*MyMethod2" + chr(13)Any method code goes in the Methods field. Any code must be preceded with PROCEDURE MyMethod1 and ended with ENDPROC.
Mark McCasland
Midlothian, TX USA