Hi Kevin,

Thank you for the great support. My respose below.

<--We plan to implement a two-part business object similar to what we did in MM VFP. The first part can be stateful and is accessed from tier 1. The second is stateless and can reside on a physically separate tier (and can be hosted in COM+), which sounds similar to what you're requesting. This design gives you the best of both worlds and allows you to place business logic in either component.

This is great! when do you think this will be ready? I'm planning for a workaround. Should I go for it?


<--I think your framework could use a schema designer. First, I can be used to set some business rules at design time. Second, it can be used to generate business and data access classes accordingly, as well as a typed data set class. Third, it will be used to synchronize table structure with the database. Finally, it can be used to implement the appropriate code (SQL/programming) to handle an important but almost always ignored database design pattern: one-to-one relationships

<--These are some of the things we're looking at for adding some RAD tools to the framework.

Well, we are currently working on one which we will try to integrate into your framework. We may consider giving it away to other MM users when its finished.


<--That is an option we had considered, but in this go-round we have implemented it at the UI level because we found our end users much preferred setting up security this way. I think you'll get a better idea of what I'm talking about when I release the updated docs that describe security.

Yes, but what happens if the same business component is used in different forms? Wouldn't it be a dupplication of effort to set security rules on every form for the same entity? Again, what happens if the same field is reresented by multiple controls on the same form and the user forgot to set the appropriate rules for one of of them. Wouldn't this create a security conflict?


<--What we've done instead is implemented interfaces in our controls, which can also be implemented in third-party prodcut controls. The code that does all the work is located in strategy classes which can be called from any UI control.

Its really good to work with a real architect!


Houssam