>>We'd like to make the rewrite fairly data driven, so the first question is: Does .NET allow the equivalent of VFP's EVALUATE(lcCommand) ?
>
>The question would of course be if you would need the Evaluate() function in the first place. The reason why I would avoid those typical FoxPro strategies (where it is practical of course) is exactly the point that it's easy to understand for fox programmers but not necessarily easy to understand by other folks. You want to avoid to build a VFP style application in NET.
>
>So my advise would be, try first solving it with common design patterns, and only if not otherwise possible use your VFP strategies to solve it.

Its very hard to justify using design patterns with dozens of lines of code while all you need is an EVALUATE or macro function. This coding for keeping the compiler happy is not my idea of productivity. Its good if you want to get ultimate performance, but it has nothing to do with RAD


I'd vote against .NET for these types of applications. It does not fit. Much better to look into SAAS development environments where most of this kind of stuff is really easy iso of trying to peg a square into a round hole and reinventing the wheel.


Walter,