>>>>>why not create your new command button from a class you've built that has the desired method? if you can do that, you don't need to use writemethod...
>>>>
>>>>You're right, that would work...but my question is, where is WriteMethod, WriteExpression, etc used?
>>>
>>>i'd guess that they're used internally when we add a method or property to an object...
>>
>>One suggested use I heard, was to add LPARAMETERS code to our methods at design time, like FoxPro does when you edit an error Method, the LPARAMETERS appears first. I have not been able to do it though.
>
>Nope, won't go. Anybody else? I don't know why something that's used internally would be in the documentation. It must be useable.


There is nothing to stop you from creating, modifying, and saving an object from withing a code segment. So while you are doing this, you can call, from within your codes, the object's WriteMethod, WriteExpression methods to modify methods and properties. Then you can save the object by using it's SaveAs or SaveAsClass methods. After saving this object, you can then turn around and instantiate it.

Paul