Double ditto!

I have not used the view class code, but I assume it presents non-defaults. There, again, is one advantage of PRG classes, they do not require listing default properties.

As for the dataenvironment - I use my own class for that. Updates and alignments are fired by form activate events.

There are more basic we as developers can look at in our programming style. For example, designing modeless solutions is not that difficult. Yet, when I am fortunate enough to get piece work from from commercial VFP shops, I note that many of them rely on nesting modal forms, inside modal form - etc.

I suppose this stems from rudimentary "one form for one file" concepts. Just a push from modal to modeless forms, for many of us, would benenfit our users and the markets' perception of VFP!

Another item - especially for those of us that rely on select statements: If we don't want to complain about file corruption, then we should refrain from indexing on every field in the table. Thsi goes back to pre-development design analysis. The rudiments are important!

>I agree, for visual classes, forms including their visual controls, the class designer can be used (creating the sketch) for sizing, positioning, coloring, and visual properties in general. When the visual requirements are satisfied, the next step is extracting the code by means of "view class code" in the class browser. Often, it's necessary to handle the code extracted, specially when grids and other complex containers are incuded. Then you have, in a few minutes, the code of visual classes, and now that piece of code is available to add the functionallity and everything that you consider "convenient".
>
>On the other hand, there are a great variety of tools to extract the code for the DataEnvironment attached to a form, I use a tool called "GenDE" provided by Michael Drozdov (Drozdov@ics.perm.su), also there is a "UnDE - DataEnvironment decoder" provided by John Koziol (you can be get it from downloads section of UT).
>
>Also, I recommend to use a tool like "visual-paradigm" for Object-Oriented-modeling before coding.
>
>It can be thought that this technique can be applied only to large systems. However, I think that the the big and the small exists only in the mind, and like all other arts, the programming requires a technique, and a discipline for mastering the technique. Then you can see some results. Then the sculpture begins to take a form.
>
>
>Gerry Schmitz, Terry Thurber, John Petersen, Viv Phillips, Greg Moss, Mike Yearwood, Hilmar Zonneveld.. Thanks a lot for your comments.
>
>
>Enrique Rivera
>
>"You are the architect in your mind"