The auto-enter date field would give you the date the data was imported. You can find the LAST date that was created.
Does that help?
That is helpful to know, but doesn't help in this situation. The particular problem that I run into is that I can import a file anytime....Sometimes days after receiving an excel file. So, if I import Monday's data today, I don't want mislead users to think the data is the most up-to-date. I may just have to deal with it, but I'm hopeful that's not the case.
How do you know that the import is "Monday's data"? If you have something (in the file name or ??), then this might be what I do:
1. create a timestamp (not just date) field in the import table. Make it auto-enter.
2. create a table for logging imports. it would have a timestamp (foreign key). it would also have other fields (your choice) for whatever you want to help you know what the import was about. and most importantly it would have a date field letting me know that this is "monday's data".
3. relate the two table on the timestamp fields and make the relationship allow creation of related records in the logging table.
4. now you can script setting the fields (all but the timestamp field) in the logging table. because it's a relationship, the foreign key will fill in automatically.
because they are related, you can see in your import table the related date field (from the logging table) what is "monday's data".