I understand now. Thank you for the examples. I did not think to append the 13 records to another table (or did I know how to) until Duane's and your suggestions on this type of design. It sounds exactly like what I need to do. Thank goodness for this forum! And thank you both for your time...
Thank you Andy. What method would you use to require fields? The 13 "action dates" are all required fields, and your correct that date13 cannot be before date12, date12 cannot be before date11, and so forth... But I can't imagine the field properties being the best place to require input or they...
I thought to do that, but every case requires a date be inputted for every Case Action until the investigation is complete. Knowing our users, they may skip a step in the process or choose the incorrect Action for a date. We have 13 required dates in the process. Your thoughts?
I have this Module in Access named basGetMaxDate:
Public Function GetMaxDate(dteNOIDate As Date, dteGarrityAdmDate As Date, dteOrderForIntDate As Date) As Date
Dim dteMaxDate As Date
dteMaxDate = dteNOIDate
If dteGarrityAdmDate > dteMaxDate Then dteMaxDate = dteGarrityAdmDate...
I followed all of the instructions in the thread I attached.
Standard module named: basGetMaxDate
Yes the fields exist in the table in my query.
UPDATE: I'VE GOT IT WORKING! NOW, IS IT POSSIBLE TO HAVE THE FIELD LABEL APPEAR, FOR EACH RECORD, SO WE KNOW WHICH DATE FIELD IS THE MAXDATE?
thread701-1400589
I added the GetMaxDate to my Query in the Field box, but am getting error "The expression you entered has a function containing the wrong number of arguments."
I've tried both of these:
MaxDate: GetMaxDate([NOIDate] ,[GarrityAdmDate] ,[OrderForIntDate] )
MaxDate: GetMaxDate(...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.