Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 5763 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hi Everyone,

I would like to get some idea of what developers do in regards to tracking Contacts in a database that uses Contacts in many different ways.

For example, say a company has records for Customers, Suppliers, Employees, Advertisers and Contractors. There could be a table for each type because a Customer is different from a Supplier which is different from an Advertiser and so on. If a Supplier decides to buy something from the company then they get entered into the Customer table, thus duplicating data. Alternatively, there could be one Contacts table, but that would need fields that encompass all of the different contact types, might get a little messy.

What do you think are the best practices when confronted with this type of issue?

Thanks,

Matt

This topic is 5763 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.