Is it best to create a new entity as a new field in the parent table or a new record in a completely new child table?
My philosophy is always to ask questions…
• Is it one or many?
• Or more precise, is it a fixed number or a variable number of entries?
• You also need to ask what it’s for and
• How you want to record it?
[1] If you only want to see a date you need to chase the client – just create a new field in the parent table and constantly overwrite the entry.
[2] If you want to know when you last tried, create two new fields – and still overwrite them. You only ever want to see 1 entry of each… ‘last tried’ and ‘to try again’.
You can improve the UI by creating a script trigger that when you enter the field:To_Contact_Next it puts that date into the field:Last_Try.
[3] Or you might want to record something about that attempt. Who contacted who, how you tried, and the results… In which case I would suggest a new table which could start to hold a contract history. Obviously by this stage a timestamp is better than a date because you might only be able to get them on or after a certain time.
In the case of a sales person or client handler, I would suggest working from a list view that sorts by field:To_Contact_Next.They would then have a dynamic list of the next people to call and when