>Hi Jess,
>
>I need to look at it more in depth, because this obviously will be a real issue for me, but here are more my impressions so far. VFP 6's framework is OK. If you were going to develop your own framework it'd be a good starting point, but it's not really comparable to the 3rd party frameworks available now. 1st, it's totally monolythic. There's no separation of the business rules from the interface and there doesn't appear to be a logical place within the framework to do so. 2nd, it doesn't have the native capabilities to deal with complex relationships like VFE or Codebook for Mere Mortals does. (Sorry, I don't know much about the other frameworks.) 3rd, It's security is just basic logon security. 4th, the code is very sparsely commented.
>
>The error handler does appear to be fairly good and there are a lot of other nice things in it so far. Of course all of the 3rd party vendors probably already have Tahoe and will most likely either incorporate the foundation classes into their frameworks or will "borrow" any functionality in the VFP framework that's missing from theirs. IOW, the VFP framework will probably help strengthen all of the existing frameworks.

Thanks for the information Mike. A friend of mine is just asking if it is still necessary to buy third party frameworks. It so happened that we have our own, exclusive for the company.