Four years ago I was in same position.
I was searching for a way to have all
classes regarding one table in one place.
For that purpose I have created business and gui objects classes
and corresponding generators that create draft vcx/s in seconds.
To be able to create good generators I had to put some
standards in creating tables....
As you can see it all goes in circle and takes for lot of planing...
FYI, framework supporting this scenario is in its 9th version,
contains code older than 12 years...
I wish you all the best in your adventure...

PS
Through the time I took some bets (ie. speed execution, gui, reps) showing that I
had some luck as VFPT fixed some differences in prgs vs vcx, libs vs single func prgs....
So expect some bets you will have to make by yourself...

>Thanks to all who replied. This is the friend of
>the guy who started this thread speaking. :)
>
>The question was not put properly or at least only
>half of it was put forth. The first half - already
>stated is the difference in speed execution. The other
>half - is the speed in development.
>
>If you think only PRG against VCX, then PRG is the
>easy loser.
>
>But picture this:
>
>You design your application in terms of classes.
>Specifically, you put the design details ( like what
>are the class names, and the members of each class )
>in text files or dbf.
>
>Next, you 'feed' this design into a CODE GENERATOR.
>The code generator then generates the following:
>1- the dbf files
>2- the nonvisual classes defined in prgs
>3- the visual classes again defined in prgs
>4- the instantiation of these nonvisual and visual classes
>
>And what do you do? Just the real meat of your application -
>the logic of the business and all. The heck with the routine
>form layout and design and all.
>
>The problem is if you design with VCX, you have to do it
>by hand one class after another! The problem also with our
>visual class designer ( or at least as far as we know it )
>is that it provides only one way traffic : you can convert
>your vcx to prg, but no prg to vcx!
>
>Thanks again to everyone who will take the time to read through
>this and give their thoughts - they will help us a lot!