Hi everyone.

As a FM newbie, I have a few questions related to a project I'm working on.

Working at a camera rental house, I am making a product register.

The challenge is how to...

A rental item is in reality several unike products put together to one "master", giving me the product name.

What I don't manage to figure out, is how to register all these unike products in a table, and link them up to a master product name.

In earlier access databases, I have solved this matter wit one table for each master product.

Hopefully I can solve this easier in FM..

Any advices here?

What is the common opinion on using value lists, compared to related tables for look ups?

Thanks...

I believe you need a table of Kits and another table of Items, where several items make up a kit. The tables need to be related by a common KitID field (this is assuming that an item is assigned to a kit on a permanent basis).

Thanks comment.

So far, I follow. What I don't manage to figure out, is how I should set up the Items table.

I have to sort among thousands of items, creating around 500 kits for the Kit table.

If I understood you're explaination correct, I have to give each Item a relation to a KitId. The Kit Id could be the same as the Kit name?

The Items related to a Kit is permanent.

Think I got it... -)

KitID is a auto-entered serial number field. You don't want to base your relationships on the kit name, because then if you change the name (even to correct the spelling), the relationship will break. Every table should have its own serialID field, and a 'child" table (Items) also needs a field for its 'parent' ID (KitID) - see attached.

Kits.fp7.zip

Yupp, got it...

Thanks comment.