What relationship do you have between "behavior" and "requests"?
With the correct relationship in place, you should not need duplicate fields in the related behavior table, you can just inlude the Date and Request fields from Requests on your layouts that are based on the Behavior table.
Both have a relationship with "Animal Table" (The main table I have everything layed out on) via the "Animal ID Number". When I tried to relate the date from Behavior Table to Requests table, the requests table would show an empty field for each date there was a "Behavior Comment" entered but no request. Is there something I missing so that it doesn't do that?
It helps to know the tables and relationship currently in place.
It seems you have these relationships?
AnimalTable::AnimalID = Requests::AnimalID
AnimalTable::AnimalID = Behavior::AnimalID
It looks like your layout shown above is based on animalTable?
and the portal on left is to Behavior?
Please describe the connection between a "request" record and a "Behavior" record.
Yes, that's how the Animal ID relationships look, along with the portal to Behavior.
At the moment there is no relationshop between Request and Behavior.
What I had tried before was BehaviorTable::Date = Requests::Date Which resulted in the extra blank fields. Am I chosing the wrong relationship?
Such a relationship would match to any pair of records with the same date, something that is unlikely to work.
I realize that there's no relationship. That's not really what I had in mind. If you want the data from these two fields to appear in records in both behavior and request tables, there's some sort of "connection" in how you use this data that would match request and behavior tables to each other. I'm asking for an explanation of how you use these tables in general and these two fields in specific so that I can suggest what table should define these fields and how you would then access that data from each of the other tables.
After taking another look at the uploaded picture of your layout, it seems you have three radio buton fields for recording info on how the animal's care. Why would you need that data to appear in the behavior table? Why in the "request" table? What's the purpose of the date fields shown to the left of each?
This would seem to be info that should be kept in the animal table and layouts based on Request or behavior can simply add these fields from the animaltable to their respective layouts.
Either that, or you need a new table that logs current and past changes to the animal's care instructions--also related to the Animal table by animalID.