Hi!

Well, maybe I was too categorical about that. Of course, you're right: major part of the application could be done with use of the designers. However, to use some advanced features, you will require to use VFP code for that at some moment. Usually it looks like creating module by designer, getting VFP code of that module and continue with VFP commands (exactly as I already described in my message in this thread for menus).

I do not think Project Manager is some kind of *designer*. It is just a tool to help organize project files. Report designer does not generate any code. Here in this thread we're talking about designers that generate VFP code by some way.

>>From what I know, VFP designers usually are for beginner and intermediate use and give no a complete number of features and abilities that you can have when using just a pure VFP commands. For example, view designer have a lot of limitations, so for advanced development of view queries CREATE SQL View command is usually used. Another example - VFP 7 have a lot of new enhancements related to creating the COM objects, though you can use most of them only when defining COM object by DEFINE CLASS command; visual class designer does not allow to use these new features.
>
>Vlad - I have to disagree with you here. While it's true that the View Designer and Query Designer are extremely limited, and it's also true that some of the VFP 7 COM enhancements apply only to code classes, I don't think that most expert VFP developers are working totally by hand. I certainly don't. I spend lots of time in the Class Designer and Form Designer, and use the Menu Designer, Report Designer and Project Manager as needed.
>
>Tamar