Hiya Rox!!

I haven't read the article but lemme post some theory: If you are working with an n-tier application, business rules and data access belong in the business and data access tiers. What does this mean? It means that under no circumstances should external programs directly call your data....this has to be an IT imperative for your shop. It also means that you have to post your business tier as a server-side component so that other programs have access to it.


>OK folks, August FoxPro Advisor just hit my desk. Page 58, "Empower Your Users to Adapt Business Rules" by Charles Blankenship - and I *ReallyReallyReally* like this approach of table-based validation of Business Rules for an app, that can be maintained over application life via UI!!! I think it's an excellent approach to developing a robust app that's rule intensive. AND it gets me around the dbc's clunky field rule message dialog.
>
>But there's one thing I don't get with this approach. Blankenship talks about "Enterprise-wide data validation" on page 65. But I don't see how having my business rules in a table is going to do me any good if my users want to ODBC access to my app's data? IOW How would you trigger validation via ODBC with this approach?