AnsweredAssumed Answered

Conventional wisdom related to human and group elements in database design...

Question asked by jppuckett on May 30, 2013
Latest reply on Nov 5, 2013 by mcurley

Simply put, in the past I would have created separate tables for the different types of contacts included in my database. In previous databases, I might end up with a table called Vendor Contacts, for contacts outside the org, and one called Users, for internal contacts. I'm trying to think through the issues I might face if I were to just make a single table of contacts and have a designation for each to be specified as a Vendor or a User. Any glaring problems come to mind if I am mixing my internal and external contacts in one table?