When to save a calculated field

[Cereldine]

Hello everyone,
I have been trying to calculate the number of working days a person has off sick between two dates.I was aware of how to calculate the difference between two dates using datediff, this was not quite hat i needed.
after much experimentation and a little searching I came across this site that has I would recommend to other beginners to use as a query and a module.

http://www.mvps.org/access/datetime/date0006.htm

I have a calculated field that uses this function to work out the number of days, My question is, Is it worth me saving this calculated field physically in my table instead of in the query?

The reason for this is that im only with company for limited time and others will be building reports in the future and would prob prefer to build reports on tables rather than queries. If so, how can I go about setting the field value to that of the query result?

 

[Mile-O]

Is it worth me saving this calculated field physically in my table instead of in the query?

No. There would be little point in wasting space and creating cause for error. It's not about saving time; it's about data integrity.

would prob prefer to build reports on tables rather than queries.

Why would they want to base reports from tables?

 

[alastair69]

You could alway have a look at this web page http://allenbrowne.com/casu-14.html. It maybe able to help you in your quest.

Alastair

 

[Cereldine]

Why would they want to base reports from tables? [/QUOTE]

Because they have limited intelligence! Cool thought was best avenue to go down, thanks

 

[KenHigg]

May I also suggest you have them tinker around in a .mdb that is seperate from the production .mdb