Hi!

If you read more about n-tire development, you will be wondered how this effect is close to what is supposed to be a result of n-tire development. Rrelly, putting business rules into the database is completely another tire in the system, because it fits into the main definition rules of the tire:

easy replacement
independence
separate location
approach to use by several applications (VFP applications with classes to work with such data and business rules).



>Fun to see a work like that in production...
>
>Regarding business rules. I wrote a conversion program which put rules for conversion into a table. Each rule returned a logical to indicate if the data fit the rule. If the record passed the test, an action was performed. Finally, the table indicated whether this test finished the testing on the field, or whether to move to another test.
>
>It was amazing how that rules layer simplified the coding. And, I was able to accomplish probably 99% of the conversion within it.
>
> Jay