I think what you need is rather
People --> Accounts --> Transactions
A person can have many (well, multiple) accounts, and each account can have many transactions, but each transaction belongs to exactly one account, and each account to only a single person.
SSNs shouldn't be stored in the Accounts or Transactions table – you link People to Accounts by a serial key, likewise Transactions to Accounts. You can of course utilize an SSN to find a person, and thereby their accounts, and transactions for those accounts …
See if this quick sketch gives you some ideas as to transaction handling. I leave the "create new person if SSN isn't in the system yet" part to you …
Thank you so much and this file helps me big time.
Hello Erolst - thanks for sharing this file. Could you enlighten me - how are the global variables ($$SSNheader and $$accountHeader) updated?
Dave Hobson wrote:
[ …] how are the global variables ($$SSNheader and $$accountHeader) updated?
• calculated in the Conditional Formatting calculation for the search field
• updated for display from within the OnModifyTrigger for that field by a simple refresh.
Just a fancy method – probably better to put those calculations in a script, so the code doesn't reside in a (relatively volatile) layout object.
Wow, thanks for that - I've never thought of using conditional formatting to update values elsewhere on the layout, which is why I didn't look there. It makes perfect sense now, and thanks very much for clarifying.