William Benson (VBACreations.Com)
vbacreations at gmail.com
Mon May 27 22:20:13 CDT 2013
Hi this may well be long-ago-covered ground, but I am stuck in a relational database conundrum. Simple world, there are companies, they have associates (people), those people have events, and those events require notification circles. For example, a driver for a trucking company, may have a medical inspection, notification of the due date for which, is to be sent to the trucker as well as the company's dispatcher (so that, after a certain date, the dispatcher will remember not to send that trucker on any routes without proof of completed medical check). I am struggling over whether to make all events tied to the company with a FK, or whether to make all events tied to an Associate, thus only indirectly tied to the Company. The reason for my second-guessing the latter approach, which on the face of things seems obvious, is scalability. Suppose there are certain kinds of events which are not related to associates, but based on the company itself. I can't think of too many of examples of these off-hand, but for example, certain marketing oriented events, or billing related events, might be worth tracking. If I chose the other approach, to work at a Company level, create an Event for that company, then choose the Associate(s) for whom the Event mattered, then it seems all bases would be covered. Am I right in leaning towards the latter approach?