2 Replies Latest reply on Sep 27, 2010 5:46 PM by PaulDabkowski

    Difficult database design, any ideas?

    PaulDabkowski

      Title

      Difficult database design, any ideas?

      Post

      Hi there,

      I have recently gained a new client. The client is a Nautilus Gym in the local area. They wish to move from their current paper file system to a digital system encompassing FileMaker on both Mac and Windows computers and iPads for roaming around the gym accessing/updating their members data.

      I am stumped on this one tho. Member details and payment stuff is simple, all done on that front. But recording the exercise data is going to be difficult. These databases have to be quick, but they are going to be HUGE. For every exercise (of which there are 32 in total, not all used by every member, that would be Chuck Norris gym work!) I need to be able to log weight settings, seat positions, reps and other information. The average member does ten exercises. I also need to keep a history of these values so that the Gym can track the progress of its members and tailor programs to work for them.  

      I am without ideas on how to work all of this out! I could set up a table for every exercise and used ID's from the MemberDetails to link it and then display it all later on another layout. But that is going to get very messy very quickly and with that many relationships and lookups happening at once I fear that it will slow down substantially. As a rough guide, the gym has approx. 200 active members.

      Anyone with any ideas? Any help is greatly appreciated!!!!!!!!

      Paul Dabkowski

        • 1. Re: Difficult database design, any ideas?
          philmodjunk

          Use one table for all excersize results and include a field that identifies the equipment needed. You may need to define a set of fields that has more fields than any one piece of equipment needs, but this can be made to work and avoids the need for different tables for each excersize.

          Think of it this way: Each time a member comes to the gym, start a "workout invoice", one such record for each visit. Each equipment or excersize that the member chooses is a product that they "buy" and it will be added to the LineItems portal of the "invoice". Instead of price and quantity fields like an actual invoice, the fields in each line item record would record whatever data about each excersize that you need to record.

          • 2. Re: Difficult database design, any ideas?
            PaulDabkowski

            Nice! I hadn't thought of it that way at all!

            That would encompass everything that I wanted to do, and would work perfectly! Thanks so much for the help.

            I should probably start to think outside the square a little more :)