Rx_
Nothing In Moderation
- Local time
- Yesterday, 21:02
- Joined
- Oct 22, 2009
- Messages
- 2,803
See attachment:
Business rules are often hard coded. This can lead to huge amounts of maintenance as the project expands.
This is a simple example of how a business rule can become table value driven. The table is exposed in a "maintence db" for the user to manage over the form's lifecycle.
A list box in this case has a few values. To follow business rules of a regulatory business, the listbox selection determins if either of two fields should be enabled.
The table with an autocounter ID allows the user to enter another value for the dropdown listbox. Note the two fields with "A" that determine if the associated text box should be enabled.
The Form Current fires anytime the data changes. The Form Current calles a Subroutine. At that time, the value in the listbox is used in a Dlookup function. The result determins if the assoicated text box is enabled or not.
Quite a few steps over hardcoding the text box. However, the end-user can be given a few instructions to manage the table and the outcome.
This is a very simple example that will grow in complexity.
However, the complexity can be somewhat documented as the rules are centrally located in both tables and subroutines.
On the Form_current - please ignore the comment in front of the call to subroutine BussinessPermitStartEndRule
Business rules are often hard coded. This can lead to huge amounts of maintenance as the project expands.
This is a simple example of how a business rule can become table value driven. The table is exposed in a "maintence db" for the user to manage over the form's lifecycle.
A list box in this case has a few values. To follow business rules of a regulatory business, the listbox selection determins if either of two fields should be enabled.
The table with an autocounter ID allows the user to enter another value for the dropdown listbox. Note the two fields with "A" that determine if the associated text box should be enabled.
The Form Current fires anytime the data changes. The Form Current calles a Subroutine. At that time, the value in the listbox is used in a Dlookup function. The result determins if the assoicated text box is enabled or not.
Quite a few steps over hardcoding the text box. However, the end-user can be given a few instructions to manage the table and the outcome.
This is a very simple example that will grow in complexity.
However, the complexity can be somewhat documented as the rules are centrally located in both tables and subroutines.
On the Form_current - please ignore the comment in front of the call to subroutine BussinessPermitStartEndRule
Last edited by a moderator:
