Houssam,

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

I don't have a projected date yet, but it will probably be at least two months.

><--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

>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.

We've had a number of developers contribute to Mere Mortals in this way...we promise to put your name in lights <s>!

>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?

In the case of the control used in multiple places, you could simply create a control subclass that can be reused throughout the application. Regarding the same field used multiple times on a form, yes, it would be up to the developer to make sure they set security in both places, however I believe the benefit to the end user is worth the extra effort on the part of the developer.

>Its really good to work with a real architect!

Thanks!