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 6647 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hello,

I have an invoicing database, with a related customer table. There is also a mailing list-type table that is used to track marketing contacts and send out targeted mailings to customers or potential customers. A third table holds information on authors. Any of the people in the three tables could become a customer that would have an invoice.

Do I create duplicate entries in the customer table when people in either of the other tables buy something? If so, how would I keep their contact information up-to-date in both tables?

Does it make sense to create one big table with all the fields from all three tables?

In the other direction, customers could become people we want to put into a targeted mailing list in the mailing list table.

I'm not sure how to handle these situations. Is there a standard way to handle this kind of thing. Neither of these options seems like a very clean way to manage data. Any ideas would be welcome.

This topic is 6647 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.