Hello all, I am after some database design advise.
I have certain values that I want to use in various areas of my database.
For example I have a field that stores an Inpection Interval.
To start with a value of 3 months will be used, but this may later change to 4 months.
At present I have a global constant in a module called IntervalReminder = 3
This value is used on various forms for text box calculations.
Of course if I change the constant to 4, the change is reflected thoughout the database.
The users however will not be familiar with going into modules to change values, so I was thinking of creating a Settings table (fronted with a form) and using Dlookup to get values to the calculated textboxes.
Functionally both ways seem to work fine, but I was wondering what the best or normal approach is. A settings table seems straightforward or, is there a way to make it easy for users to change constant values without opening the module?
Many thanks for any direction / comments. Mark.
I have certain values that I want to use in various areas of my database.
For example I have a field that stores an Inpection Interval.
To start with a value of 3 months will be used, but this may later change to 4 months.
At present I have a global constant in a module called IntervalReminder = 3
This value is used on various forms for text box calculations.
Of course if I change the constant to 4, the change is reflected thoughout the database.
The users however will not be familiar with going into modules to change values, so I was thinking of creating a Settings table (fronted with a form) and using Dlookup to get values to the calculated textboxes.
Functionally both ways seem to work fine, but I was wondering what the best or normal approach is. A settings table seems straightforward or, is there a way to make it easy for users to change constant values without opening the module?
Many thanks for any direction / comments. Mark.