Hi all,
Hope everyone is well!
Quickie for you:
Two Tables: Doctors & Applications, 1 - M relationship. Main Form shows Doctors info, with Subform based on Applications. Simple enough.
In the Applications table, I have an Active field.
What I need to ensure is that JUST BEFORE creating a new application record for THIS doctor in the subform, the user MUST set any existing Active=TRUE fields in other records to FALSE (unticking a checkbox).
I have it working so that creating a new application record has 'Active' set to TRUE (ticked).
I think there is great work being done on this site, and this problem is actually for my wife, but she has no internet access, so I am helping out.
*
*
*
*
*
*
PS: I know it is principle to name related fields with the same name, but I always set up a table field that will be a foreign key field to begin with 'TableName_Code';
i.e. based on the example above, Doctors RegNo is linked to Applications Doctors_RegNo.
The reason is if you start naming fields the same, it is not obvious where tables with multiple links are actually linked to. What are your views on this?
Hope everyone is well!
Quickie for you:
Two Tables: Doctors & Applications, 1 - M relationship. Main Form shows Doctors info, with Subform based on Applications. Simple enough.
In the Applications table, I have an Active field.
What I need to ensure is that JUST BEFORE creating a new application record for THIS doctor in the subform, the user MUST set any existing Active=TRUE fields in other records to FALSE (unticking a checkbox).
I have it working so that creating a new application record has 'Active' set to TRUE (ticked).
I think there is great work being done on this site, and this problem is actually for my wife, but she has no internet access, so I am helping out.
*
*
*
*
*
*
PS: I know it is principle to name related fields with the same name, but I always set up a table field that will be a foreign key field to begin with 'TableName_Code';
i.e. based on the example above, Doctors RegNo is linked to Applications Doctors_RegNo.
The reason is if you start naming fields the same, it is not obvious where tables with multiple links are actually linked to. What are your views on this?