Not So Simple Value List

[Jay Pifer]

On the data side:

I am building a database that includes hotel information for generating job tickets for service calls. Each hotel has 2-3 ballrooms and 2-3 hotel contacts.

On the data extraction side:

In a different layout, I need to generate a service ticket for a specific hotel. I want the option of a pop-up value list to display the related ballrooms (so that we may designate which ballroom) and another value list to display the related hotel contacts (so that we may designate which hotel contact).

This is what I have done:

On the data side:

I designed a form to enter the hotel data. For the

[Wim Decorte]

You wouldn't use repeating fields for ballrooms and contacts, you would use different tables with relationships between them.

Hotels table --> ballroom table (based on hotelID)

hotels table --> Contacts table (based on HotelID)

The value lists are then built to show only related info from ballrooms and contacts.