Aug 04 2023 10:21 PM
Hi,
i am attempting an access DB for a dog rescue. i have a table for people, one for dogs and one for status' (i.e. been surrendered, been fostered, been adopted).
in my dog table i have FK for the person and the dog's current status.
i would like to keep a record of any changes to a dog's status, i.e. when they're fostered (and by whom) and then when they're adopted (and by whom). i created another table (statusUpdate) that has FKs for the dog, the person and the status and i also have a date field.
my issue is that i don't know how to update both the statusUpdate table as well as the dog table to reflect what the current status is and who the dog is with.
i'm pretty sure it's a case of me not grasping a pretty simple concept. any assistance would be greatly appreciated.
regards,
g
Aug 05 2023 03:11 AM
Aug 05 2023 11:52 AM
thanks. so i currently use a form to add people and another to add dogs. i take it that i would then need another entry form to add the link between the person and the dog and the dog's status?
i'm trying to make data entry as simple as possible as the people likely to use the DB are not the most computer literate. 🙂
thanks again,
g
Aug 05 2023 12:03 PM
Aug 06 2023 12:21 PM
Aug 06 2023 01:20 PM
If you enter a new dog on the form for the dog, you can immediately enter the first status on the subform. If the person is also new, it is better to enter this in advance. Then you can immediately choose the person when entering the status.
I've put together a very simple sample database to demonstrate those principles. See attached file.
Aug 06 2023 02:40 PM
Aug 06 2023 11:59 PM
Aug 07 2023 11:00 AM
Aug 07 2023 11:41 AM
Aug 07 2023 01:14 PM - edited Aug 07 2023 01:15 PM
On your form addDogF the AllowEdits property is set to No. This means you cannot edit anything on the mainform nor on the subform. Set it to Yes and you can add/edit values on the subform.
Aug 07 2023 01:55 PM
Aug 07 2023 01:59 PM
Aug 07 2023 02:01 PM
Aug 21 2023 02:38 PM
Aug 22 2023 12:48 AM - edited Aug 22 2023 12:51 AM
You need at least one more table. A committee has multiple people and a person can work in more than one committee. So you need a junction table (people-committee) with (so far) two foreign keys (no foreign key to people in the committee table).
A person has a role in a committee. Someone else can have the same role in an other committee. A person can have (different) roles in the committees he is in. Bottom line is: role is an attribute (fk) in people-committee (no fk to role in committee). I assume a person has only ONE role in a committees.
Aug 22 2023 02:04 PM
Aug 22 2023 02:43 PM