K
Keypad
Hello,
My previous database was saving the results of DateDiff into a field in my
table. I learned a better approach was to use a query to get the days
remaining between two dates and perform an action on the fly, instead of
saving data to a table. That worked well until I noticed that when DateDiff
counts down to the end of the year, on the following day it begins it's count
again starting at one.
That won't work because in this case I would have act on the day of
expiration otherwise it's a mute point for any membership that goes beyond
expiration.
So, my question is how do you handle this situation without saving data?
KP
My previous database was saving the results of DateDiff into a field in my
table. I learned a better approach was to use a query to get the days
remaining between two dates and perform an action on the fly, instead of
saving data to a table. That worked well until I noticed that when DateDiff
counts down to the end of the year, on the following day it begins it's count
again starting at one.
That won't work because in this case I would have act on the day of
expiration otherwise it's a mute point for any membership that goes beyond
expiration.
So, my question is how do you handle this situation without saving data?
KP