Hi Don,

>
>I have seen and worked with an older version of MM.NET and as I recall, it was nicely done.
>
>We would like to avoid having to start over from scratch. Given that consideration, I suppose the questions are:
>1) What traps or pitfalls will we have in trying to combine both DotNetNuke and MM.Net; 2) are we better of going with one of the DNN form/controls vendors.
>
>Thanks
>-DL

Since I am not very familiar with DotNetNuke I am not sure I am the best resource for that. I just looked at the DNN website and could not get a good feel for how it works. I may need to download it and see what it does more behind the scenes. Maybe Kevin will jump on and have a better answer for your questions.

It looked like DNN does data access but it also mentioned not needing any programming experience. I find that very odd and would wonder how it provides a very robust data access in an n-tier fashion. Much of the MM benefit comes from the security, localization, and Data binding added to the controls. That said, you can use MM framework without the MM controls and you can use MM data layer with other controls. Keep in mind MM provides a framework for the application as a whole that is very beneficial but having the controls invovled in security as well as data binding is a major plus. All that said, I don't know enough about DNN at this point. I will have to explore more about that.
Tim