2 Replies Latest reply on May 12, 2010 11:00 AM by aammondd

    Building a related table?

    AAgraphics

      Title

      Building a related table?

      Post

      Hello.  We are using FMP 10 on Mac and PC

       

      This is a general summary of what we have in FMP 10:

       

      We have a web host that hosts the FMP database.  The employees of the company access the database using FMP and their internet connection.  The database and main table shows all of the products that are under development.  There is a related table that has all of our vendor information.  Our vendors are able to access our project management system (PMS) by using their internet browser by using FMP IWP feature.  Vendors can log in using unique usernames and passwords and they can see a list of only their projects so they can enter ingredient listings and nutrition facts information for each specific project.  This works wonderfully.

       

      We are looking to add another feature and I am not sure how to go about building it.  Here is what we would like to do:

       

      About six vendors will quote on each product we develop.  We now want vendors to be able to log into the system and enter their quote directly into our system, but we do not want them to see the information of the other five vendors.  What is the best way of building this?  We use about 60 plus vendors, so the combination of vendors for every product varies.  Any thoughts?  Does this make sense?

       

      I was thinking that I could possibly build six new tables and have them related back to the main table by using the item number and go from there.  Does this sound like a disaster?

        • 1. Re: Building a related table?
          philmodjunk

          You should only need one quotes table. Since each vendor has their own account and password, you can use security settings to keep them from seeing any quote records that aren't identified with their account name.

           

          You might also set up a layout that displays a project with a portal that lists quote records. If you set up the portal's relationship to match only quote records that are marked with the current record's ID and the the current user's account name, you'll have filtered all the other quotes out of the portal.

          • 2. Re: Building a related table?
            aammondd

            You shouldnt need six tables just auto enter the username in a created by field and then you should be able to use similar logic that restricts vendors to their own items for ingredients) through a  relationship based on the UserName. If you capture the Unsername in a global field at login then you can link through it to filter out records you dont want them to see.

             

            there may be a simpler way but this is what comes  to mind at the moment.