3 Replies Latest reply on Jul 8, 2010 8:43 AM by philmodjunk

    Audio Patching Sheet

    BenHarris

      Title

      Audio Patching Sheet

      Post

      I am relatively new to the FileMaker platform, and let me start by saying what an amazing and powerful piece of software it is!  

      I currently have an excel spreadsheet that we are using to coordinate the stage patching for an audio company I work for.  The patch sheet has a main input list which displays, in order, where a certain instrument will show up on the main snake line.  It also has a field which displays which sub-snake box that channel is coming from. We have four subsnake boxes: green, yellow, blue and red, which are fed to the main snake box and then go to the respective audio console.  In the spreadsheet you type the respective color and subsnake number in the SUB column of the main patch list.  IE: to specify input 1 as a signal coming from yellow subsnake input #1, you would type Y1, for yellow subsnake input #2, you would specify Y2, etc.  After you specify the subsnake input, the appropriate subsnake is automatically populated with the main snake input number and instrument label.

      I am looking for a way to accomplish this same thing with FileMaker.  We currently run our business on filemaker, using it to book shows, rentals, keep track of repairs, clients, scheduling etc, so I am trying to implement this module into our current system.

      What would the best way to go about accomplishing this goal?  I am a relative newbie when it comes to filemaker and would welcome and help or advice you can give.  I've included links to both our original patch sheet and the filemaker file in which I started tinkering with.  I may be going at this the entirely wrong way.  

      Excel version: http://benharris.net/fm/patchexcel.xls

      FM version: http://benharris.net/fm/patchfm.fp7.zip

      Thanks for everything.

      Ben

        • 1. Re: Audio Patching Sheet
          philmodjunk

          In filemaker, the key is in how you set up relationship in Manage | Database | Relationships.

          Please note that I haven't had time to download and look at your file, but from the description, it sounds like you may need a portal on your "Snake" record that will list your "subsnake" records. Your patch sheet would appear to be a list of "Snake" records. Whether or not you need a portal, you'll need at least two and most likely more tables to make this work. At the very least you'll need one table where each row of your Patch sheet is a record in this table and a second table describes the information for each "subsnake".

          I could be wrong here as I am unfamiliar with your industry and that can make your industry jargon a bit obscure at times.

          • 2. Re: Audio Patching Sheet
            BenHarris

            Thanks for the reply!  This seems to be exactly what I want to do.  Create a relationship between the table that contains the main patch sheet and the 4 subsnake tables (red, green,  blue, red).  If the values of the inputsub field in the main patch table match criteria of the relationship between one of the subsnake tables, then it will create a value in said subsnake table the subsnake number and the instrument name and use a portal to display this information on the main patch sheet layout.

            This all makes sense, the question is , how do I create a "conditional" relationship that will only pull information if a value starts with the subsnake color (R for red, or G for green, etc. and channel 1-12, so R1-R12, G1-G12, etc.)  I know this is probably confusing as a lot of it is industry related and would make more sense for someone who is in the industry, but I really appreciate any tips or help!

            Thanks!

            Ben

            • 3. Re: Audio Patching Sheet
              philmodjunk

              What version of filemaker are you using? New to filemaker 11 is the ability to create a filter expression that limits what you see in the portal to only those related records meeting the filter expression's criteria. With older versions, you can get the same result, but need additional table occurrence boxes and relationships in the relationship graph.

              I'd put color code in one field and channel in another. I can always write a calculation field to combine the the two codes for display purposes if I need to. That also allows you to use value lists for color and channel assignements to cut down on data-entry errors.

              In filemaker 11, you can use a filter expression such as: Subsnake::ColorField = "R" to filter out all related records except those that are for the "red" subsnake or I can use MainTable::gColor = Subsnake::ColorField to set up a filtered portal where I can choose a color code in gColor and see only those matching records in the filter.

              In older versions, (and it sometimes remains a good option for filemaker 11), you can build the condition into a relationship:

              MainTable::SnakeID = SubSnake::SnakeID AND
              MainTable::gColor = SubSnake::ColorField