Ok- not sure I did a great job of wording that question. It might be easier to share the specifics.:
The population we are tracking with the database moves frequently. We would like to track their new addresses, of course, but keep the original city from our first contact with the person while minimizing extra data entry steps.
It feels like there are two possible solutions:
Add a "CityAtEntry" field to the underlying table.
Add a corresponding form field control to the intake data entry form controlled by the City entered in the regular data entry form, so no one has to enter a city twice.
But for that method to work, I'd need to have the source of the form field control one thing (City Data Entered text box) and have the data entered into the form field control save to an underlying table as a separate thing (CityAtEntry).
I don't think I can split the underlying source for a control like that.
Solution 2. Absolutely will not work- too much is required of the user:
But would require manually saving "CityAtEntry" on a form when the person has a new address.
Any ideas for a prettier solution?
Thanks in advance.