OK - I created a new table called 'CurrentYr'.
It only has 1 record - a constant - 2016 - No primary key
Only one item in the table
OK - I created a new table called 'CurrentYr'.
It only has 1 record - a constant - 2016 - No primary key
Only one item in the table
Why did you create a new table if you already had a table with the data?
Did you see post 15?
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
I thought having a simple table with just one item would be easier for the user to change.
Users should not work directly with tables and queries, only forms and reports. You can have a form display only the record(s) user needs to see.
And does that mean you now have to maintain the Current Year value in two tables?
Options for retrieving the value.
1. DLookup() expression:
=DLookup("SomeFieldNameHere", "[CurrentYr]") - [BirthYr]
2. query that includes the new table - without a JOIN clause
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Thanks to all. I will stick with going into deign view and changing the year.