David Gay wrote:
The standard approach seems to be putting the conditional/constraint logic in each usage point (form/screen level). My programmer's understanding suggests that these constraints would be better located in the view-entity's declaration (since they never change and can be localized in one place).
No, they wouldn't be better placed there. Keeping conditional logic out of the entity definition allows the entity to be used in other places - with other conditions.
Our questions are: - Have we missed some already-available functionality (at the entitymodel.xml level)? - Is there a best-practice for this situation, or is it more of a "this is just what people are doing" thing? - Are there arguments _against_ either of the above extensions? We really want to do the right thing with this. :-)
The main argument against embedded SQL is that you lose platform independence.
-Adrian
