Losing the Today Calc on Start-up

[mborgens]

I want to preface this with secure knowledge that it has already been addressed somewhere on these boards. I cannot find the threads; so, here it is again.

I have some very large related databases that are running on a network. I have had the luxury of having a secretary that arrives prior to anyone else to launch the program. It's a pretty spiffy network so it doesn't take too lone to calc the Today feature in two of the files. It's time to lose it and internalize the Today feature. What do I do? Any answers? Even if someone could direct me to an existing thread.

Thanks much.

[LiveOak]

Use "Status(CurrentDate)" in calculations instead and make them unstored.

-bd

[mborgens]

Thanks for the response. Am I going to notice any speed delays? Also, do I replace every Today with Status(CurrentDate)?

[kenneth2k1]

I don't think youll notice any speed problems because it is an unstored calc.

The today function could cause a problem because if the db is left open overnight, "today" still thinks it is yesterday. Apparently it has its place, though. The following link is a post by Vaughan regarding some aspects about the today function:

http://www.fmforums.com/threads/showflat.php?Cat=&Board=UBB16&Number=36835&page=9&view=collapsed&sb=5&o=&fpart=1

[mborgens]

I believe the article is relavant to my database. I wanted a popup that popped up with today's date as an option. Because value lists need to be stored to work, the only way that it works correctly on a network is to have an indexed field with Date as the calculated result that equals Today. I use this numerous times (approx. 50+) in my solution. So, am I stuck? Status(CurrentDate) shouldn't work because it needs to be unstored to calctoday's date.