Bernard Piette wrote:
here's a note from utteraccess and wondered what you thought about it...

"Also I do not recommend composite Primary keys"

That would come as a surprise to hundreds of thousands of commercial
database developers all over the world!

There is absolutely nothing wrong with composite primary keys. They are
the natural choice for child tables in parent/child relationships. It's
nonsense to say that they have any bad performance impact.

Of course, "everything in moderation". If I had 10 levels of 1:m
relationships, I'd certainly be reluctant to have a 10-field PK in the
bottom-most table! I'd probably introduce an autonumber PK, at some
point in that structure. But it's rare to go anywhere near that deep,
in my opionion.

HTH,
TC