Nagasaki Posted August 30, 2006 Posted August 30, 2006 Hi, I am not sure if this question even goes here, so forgive me if I posted it in the wrong place. What exactly is the benefit of setting up different tables in one database? Right now, I have built a database that I am going to use to manage a collection of artwork, and I have everything - from the item information, provenance information, valuation information, listed in one table. Would to break these different areas up into different tables? If I want to build a seperate area to search just for artist contact information, should this be in another table. Thanks for your help!
John Mark Osborne Posted August 30, 2006 Posted August 30, 2006 Yes, you should set up the artists in a table separate from the artwork. This will allow you to update the information about an artist and have it flow through to all the artwork records. But, you really should get a good understanding of relational design before starting your project. I would recommend the Professional Foundation Training (PTS) manual and/or class. The PTS book can be found at the filemaker.com web site for $99.00. Hands-on classes covering the book are available at: http://www.databasepros.com/
Recommended Posts
This topic is 6661 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 accountSign in
Already have an account? Sign in here.
Sign In Now