Hank:

Builders would be nice indeed!

How about adding an active data dictionary?

I agree with the major loss of productivity when it comes to creating Windows apps, but building gourmet or burger joint web apps at least in my experience are both faster with .NET, since you don't need a third party tool (i.e., WWWC, ActiveAFP, etc.) to do any of that.

Of course, given the way VFP OleDB works right now, you are much better off giving up on VFP backend and move to SQLServer, MySQL, etc.


>BuilderD, BuilderB; heck, just give me aselobj() <s>
>
>The common thread through all the VFP user's comments about .NET is very simple: if I make the switch, I will lose my productivity, even after I learn the gazillion .NET classes.
>
>Application production is different than application creation, in the same way that being a chef is different than being a gourmet cook. Both may turn out the same product; but the chef does it about 5 to 10x the speed of the gourmet cook, and has to, in order to stay in business.
>
>Hank
>
>>>Hi Ken,
>>>
>>>I've read a few articles and papers on creating builders in .NET, and while it's doable, it's still a very big pain. I'd love to see a paper that created a framework for building builders that made it as easy as it is in VFP. Custom builders save us about 50% of the time required in designing forms, minimum.
>>
>>Sort of like a BuilderD for .Net. That would rock!
>>
>>BOb