Is there a problem with having two unique primary keys in the same table and layout? I want to track two different types of customers in a single customer table rather than making two separate tables. Is this unusual and am I asking for problems?

Thanks

There is nothing wrong with your desired outcome. But a Primary key signifies only ONE unique record per table. That doesn't stop you from designating two types of customers and you are correct that you don't need two separate tables. Just have a field called CustomerType which would contain your groupings, such as: Retail, Wholesale, Store, or however you wish to designate them.

Then create a value list called CustomerType. It can be based upon values from field (CustomerType) or a Custom value list. Users would select the Customer type from radio buttons.

Primary key - only one per record per table - unique, meaningless and never-changing.

LaRetta