D
Douglas J. Steele
Because it's a violation of database normalization principles, Access
doesn't allow you to create calculated fields in tables.
What you can do is create a query that does the calculations for you, and
use the query wherever you would otherwise have used the table.
For instance, if you've got StartingDate as a field in your table, you can
add a computed field OneYearLater: DateAdd("yyyy", 1, [StartingDate])
--
Doug Steele, Microsoft Access MVP
(No private e-mails, please)
fields to reflect the new starting date and the updated 1 year.
possible Flag) 1000 hours, 1500 hours and 3000 hours from the starting hours
and then update.
perform.
doesn't allow you to create calculated fields in tables.
What you can do is create a query that does the calculations for you, and
use the query wherever you would otherwise have used the table.
For instance, if you've got StartingDate as a field in your table, you can
add a computed field OneYearLater: DateAdd("yyyy", 1, [StartingDate])
--
Doug Steele, Microsoft Access MVP
(No private e-mails, please)
following is what I am trying to do:Cindi said:I am trying to create a few formulas in a database I am designing. The
year from this starting date and when that date is reached to update both1) I have a starting date. I need to show in a separate field the date 1
fields to reflect the new starting date and the updated 1 year.
number of hours each machine is worked each week. I need to show ( and2) I have starting hours on a machine. An additional field I have is the
possible Flag) 1000 hours, 1500 hours and 3000 hours from the starting hours
and then update.
companies that these details have been met and they have duties they have to3) As the aformentioned dates and hours are met, I need to email the
perform.