The Relational Data Model, Normalisation and effective Database Design
Fundamentals of Relational Database Design -- r937.com
essentially you need to associate your entities when defining keys
each and every table in a relational database MUST have a means of uniquely identifying a specific row within that table. a table may have one or more indexes, one or more of which can be unique (but having two unique indexes in a table ius relatively rare in the real world)
so you need to look at how items in table X are related to table Y
ferinstance a Vet probably needs to know who owns a pet (so it can rob the owner blind, sorry charge the owner for services)
ferinstance a pet will usually have an owner
on your current model you have a column dog/cat
/ is a reserved symbol in Access meaning it should not be used for table or column names
there are other things to consider
can there be more than one owner of the pet?
can there be more than one vet in a vets practice?
should there be more tables defining the pet?
ferinstance should there be a pet type table (so its no longer dog/cat, but dog / cat / hamster....
should there be an intermediate table between pet type and pet that identifies the type /breed of pet
its never smart to use alpha columns such as a name as a foreign key.
because some computer systems see John1302, john1302 or JOHN1302 as different spellings. there also used to be a concern about storage but that should be less of an issue these days
I'd rather be riding on the Tiger 800 or the Norton