B.Gordon Posted March 14, 2005 Author Posted March 14, 2005 I have a DB that manages a schedule. I have a table that dates get put into and kept to show a history. I am trying to make a field that shows the "next appearance date" where it parses the related appearance date history table and shows the latest entry which would be a date in the future. Any thoughts on how I would constrain this "next appearance date" to show only the latest date in the history, which unless we mess up the data entry or forget to update the record, should be a date in the future...
B.Gordon Posted March 14, 2005 Posted March 14, 2005 I have a DB that manages a schedule. I have a table that dates get put into and kept to show a history. I am trying to make a field that shows the "next appearance date" where it parses the related appearance date history table and shows the latest entry which would be a date in the future. Any thoughts on how I would constrain this "next appearance date" to show only the latest date in the history, which unless we mess up the data entry or forget to update the record, should be a date in the future...
B.Gordon Posted March 14, 2005 Author Posted March 14, 2005 I have a DB that manages a schedule. I have a table that dates get put into and kept to show a history. I am trying to make a field that shows the "next appearance date" where it parses the related appearance date history table and shows the latest entry which would be a date in the future. Any thoughts on how I would constrain this "next appearance date" to show only the latest date in the history, which unless we mess up the data entry or forget to update the record, should be a date in the future...
-Queue- Posted March 14, 2005 Posted March 14, 2005 If I understand correctly, you can create a relationship between an unstored calculation date field of Get(CurrentDate) to the date in your related table, and use the < operator (assuming the CurrentDate field is on the left-hand side) so that all related dates are greater than the current one. Then you can put the related date field on your layout and it will display the first related date that is greater than the current one. If the 'next' related date is dependent on a static date field and not the current date, then use that date field instead of the unstored calculatione one.
-Queue- Posted March 14, 2005 Posted March 14, 2005 If I understand correctly, you can create a relationship between an unstored calculation date field of Get(CurrentDate) to the date in your related table, and use the < operator (assuming the CurrentDate field is on the left-hand side) so that all related dates are greater than the current one. Then you can put the related date field on your layout and it will display the first related date that is greater than the current one. If the 'next' related date is dependent on a static date field and not the current date, then use that date field instead of the unstored calculatione one.
-Queue- Posted March 14, 2005 Posted March 14, 2005 If I understand correctly, you can create a relationship between an unstored calculation date field of Get(CurrentDate) to the date in your related table, and use the < operator (assuming the CurrentDate field is on the left-hand side) so that all related dates are greater than the current one. Then you can put the related date field on your layout and it will display the first related date that is greater than the current one. If the 'next' related date is dependent on a static date field and not the current date, then use that date field instead of the unstored calculatione one.
Recommended Posts
This topic is 7265 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now