Hi Paul,

>I'd take a look at Visual Fox Express. It's still being actively developed and supported, supports n-tier architecture, and (since you've use MM's) won't have such as steep learning curve. Some of the built-in wizards make it a snap to build some of the more basic data-maintenance forms. It's pretty bound to meta-data, which can be a good (and bad) thing. Good in that it's flexible, bad in that I've found tracing through meta-data driven apps. can be maddening. I'm not currently using it, but we did evaluate it in the past. If this is going to be worked on by a bunch of developer's at the same time, I'd ask Mike & Toni about how to sync the meta-data. That was a sticking point for us (I've heard they've come up with a solution for it).

If we decide to look closer at VFE, I will definitely take your advice on contacting Mike & Toni on the meta-data sync issue.


>I've use Maxframe in the past and it was pretty easy to get into (although it was definitely "monolithic" at the time). The various code styles kind of bugged me, though. I was used to the more consistent code Kevin wrote. It had a lot of code which works around various quirks in VFP behavior, which can be nice. I can be obsessive about UI stuff, but there are work arounds for things I just never noticed (Drew paid a lot of attention to some things I probably wouldn't have; I mean that in a good way).

In the beginning, some of the Maxframe code was written by several of Drew's companions. I don't know if that code was ever re-written by Drew? Anyway, having been around him in user group meetings, etc., I could see that the man knew his stuff, that's for sure!

As always, I certainly appreciate your input and insight. Thanks Paul!