Gerry,
I agree that two-way tools would be great. There are things that are easier done visually and others that are much easier in code. However, I find the implementation in VB has some serious shortcomings too. For example, if you have code attached to a form object and then delete the object from the form designer, all the associated method code won't be deleted. A similar problem is when you rename an object, then the associated methods won't work anymore since the name change is not propagated to the code. This is my (limited) experience with VBA. Maybe I'm missing something but this has surely caused me some problems.

I think Delphi has better two-way tools. I always hoped that there would be some 3rd party tool that would allow something like ScxToPrg and PrgToScx. Interesting enough, SCCTEXT.PRG contains some comments about two-way support, but it's not implemented :(

>- design the Form "visually"
- save it as "text"
- then have the !!! >>> option <<< !!! to add "code" using whatever editor one prefers ... going back to (only) the "visual tools" when it is necessary to tweek the GUI.<