>The way I handle apps that have many rules, especially ones that the rules may change, is via a table. I would suggest that you have a table with a structure like the following:
>
>Column Field Type
>primary key I
>module C(10)
>condition M
>errormsg C(100) or a Memo
>
>This way, based on the form/module that you are in, you can query this table for all of the pertinant rules. Once the rules have been retrieved, you can issue an EVAL() on the condition value to determine if the data passes/fails the rule.
>
>For ease of updating, you may want to make this a free table.

Kevin,

Doug is right. In recent years I have been involved in attorney reinsurance and actuarial calculations and using tables is a great way to keep everything straight.

Renoir