Can anyone help me; I run a one man band repair workshop where I repair customers units (TV’s DVD’s etc.) and need some advice on setting up a database. My idea was to have 3 tables 1 for ‘Customers’, 1 for ‘Units’ and 1 for ‘Fault and repair’ details with them linked by ID fields in each table i.e. ‘Customers’ to ‘Units’ (one to many) and ‘Units’ to ‘Fault and repair’ (one to many). I would like to create a layout with the customer’s details on it, a list of units the customer owns and as I select each unit the fault and repair details come up. This information also needs to be added to when new customers come along or if the customer buys a new unit or reports a fault on an existing unit. I did create a working database using Microsoft Access to do the above about 6 years ago but want to change over to a Mac and Filmmaker now. I just need some pointers in the best way to go about this and if my idea is possible or not.. Thanks in anticipation for any help.

The 3 table structure sounds fine as do the relationships, you will how ever have to search around a bit if you dont know exactly how portals operate and how to manipulate related information in general.. search around the forums, information is plentiful...

genx

I think this harder to do with FMP but attached is a quick example of how you might approach it.

OneManRepair.zip

Thank you sbg2 for your help. That is incredible you are so cleaver, I had no idea I would need extra tables and the relationships that have been created. I am working my way through what you have done and will learn a lot. Thanks again for you help