Isskint
Slowly Developing
- Local time
- Today, 01:39
- Joined
- Apr 25, 2012
- Messages
- 1,302
Hi all
I have a currency table that stores the currency name, trading code and exchange rate. I also have a TRUE/FALSE field for the default currency (the base currency being used by the company using the database). At any one time only 1 currency can be the default.
Currently I use Before Update events (on several forms) whenever the default box value changes, to confirm the user wants to change the default currency.
Much to my disapproval, one company has demanded restricted user access to the tables (so they can make 'quicker' 'easier' - more like 'lazy' and unrecorded - changes). As a result someone made a second currency a default which has led to a couple of weeks of incorrect calculations.
Is there a better way to ensure only 1 record has a TRUE value? I am thinking Table validation rules but cannot see how to use Domain Aggregate functions.
I have a currency table that stores the currency name, trading code and exchange rate. I also have a TRUE/FALSE field for the default currency (the base currency being used by the company using the database). At any one time only 1 currency can be the default.
Currently I use Before Update events (on several forms) whenever the default box value changes, to confirm the user wants to change the default currency.
Much to my disapproval, one company has demanded restricted user access to the tables (so they can make 'quicker' 'easier' - more like 'lazy' and unrecorded - changes). As a result someone made a second currency a default which has led to a couple of weeks of incorrect calculations.
Is there a better way to ensure only 1 record has a TRUE value? I am thinking Table validation rules but cannot see how to use Domain Aggregate functions.