>Cris:
>Could you elaborate on your thoughts on CM vs. CB(MM).
>
Hi Mike,

Well, I don't know much (read as nothing <g>) about .NET at this point in time. However, from what I have heard its not going to be a point and click switch from MM.FOX to MM.NET. But I admit I do not know. Anyway, if the MM.NET embraces the same concepts and logic as MM.FOX does, then the migrate to .NET with that framework would seem to me to be less 'painfull'.

As far as comparing CM to CB, I would not be able to give much good advice there; since I never really used the MM version of CB and I've only coded a couple apps with CM. But, the CM appealed to me because of it's n-tier features, its ability to quickly create apps using direct access to .dbf files, and its IDE integration.

At first I was leary of CM taking over the VFP data binding in the ways that it does, but it seems to work well. To me the CB use of lv_viewname and rv_viewname is a very good idea. In fact, I used CB so much with those views that coding for direct .dbf access is almost foreign to me.

As I have been digging deeper into CM, I am finding that the data layer and its rules object are perhaps better suited to n-tier than what CB has to offer. But, the CB I used still had the BO that was loaded with controls and dropped on a form. That changed in MM if I remember correctly.

Lots of words to say nothing I guess <g> Both are good frameworks.

Cris