2 Replies Latest reply on Nov 22, 2013 12:15 PM by disabled_dconnect

    Database design check with experienced users


      Database design check with experienced users


           I'm ready to make my database, and I wanted to check with experienced users first that I'm not making any mistakes in the design, or if there's a better way to do it.
           I recruit senior managers. I need a database that has both the company details and the candidate details in one table layout.
           I have 2 Excel sheets that I use at the moment.
           1 Excel sheet is for clients: this sheet has contact details such as the address and phone number of the company. It also has the directors I talk with that hire candidates from me. 
           The 2nd sheet has all my candidates on it. The problem is that quite often the directors I speak with are also my candidates so they are on both Excel sheets and this will create problems when my business grows.
           What I plan to do with Filemaker:
           I will create two tables:
           1) Clients (only company details)
           2) Candidates (only candidate details)
           The companies on the clients table will have an number ID, and this will match the companies' ID on the candidate table, creating the relationship between the two tables in FileMaker.
           I will create a layout in the Clients table that has two portals. Both portals will show fields from the candidates database and candidates that share the company ID of that company record on the Clients table. One portal will filter out junior managers and one will filter for senior managers.
           I think I don't need to make it anymore complicated than (i.e. making with a join table …) to get both these Excel sheets working together.
           Please let me know what you think/suggestions.
           Thanks for reading this!

        • 1. Re: Database design check with experienced users

               This is not a recommendation, but rather an option to explore:

               Seems like you have two tables that store names and contact info. In one table you have names of companies and contact info and the other, the name of people and their contact info. Some database designs might thus put both in the same table. But whether or not this is the optimum design is something that relies on how you need to use these two groups of data.

               Also, in this day and age, there are many ways to electronically reach a contact. I thus set up a related table with one related record for each phone number, email and social networking site that I want to record for a given contact. You may also want a related table for addresses if you have the need for more than one set of addresses for a given contact such as a company's physical address and what might be a separate billing address for corporate headquarters.

          • 2. Re: Database design check with experienced users

                 Thanks Phil,

                 I've taken you up on the idea of creating a separate table for the addresses, and it works well.

                 I've learned a few more things with FM, and I'm pressing ahead with creating the database.

                 Many thanks,