First off I just wanted to thank mr_vodka publicly for already helping me make tremendous strides in my database. I really do appreciate it.

I have clients who own multiple homes:

Smith owns:

1 A

1 C

4 D

6 J etc.

Johns owns

1 X

3 D

8 F etc.

This is all solved outside of the computer world because we assign ID numbers to each of the properties, but no one remembers the ID numbers so I want to first reduce the options by name and then to property.

I have a layout where the clients call in and request maintenance to their properties. The office manager will get their last name (currently a pop up related back to the property layout-working perfectly) now I want the 'location' field to be dependent on what name was picked from the 'name' field.

So the name smith will only show his properties.

Is this plausible?

Thanks for all your help.

This can be approached a couple of different ways. If you have a table(ie. Locations) in which each record contains a property/location name field and a person name field, you could create a relationship between the Name field in maintenance request Table Occurrence and the person Name field in the Locations Table Occurence. Then, make the Value List for location on the maintenance layout a value list using the new relationship.

Did that help?

OK I figured it out, so yes it did help. But to get that to work I had to eliminate a relationship I had that referenced back to the location table which had a portal summarizing all the work requests for that property.

You mentioned their were many ways of doing it....?

Thanks again for your help

Edited September 22, 200520 yr by Guest

To avoid having to remove that relationship, create two new Table Occurrences(TO). One for the WR table and one for the Property table and make a relationship between the two from Name(WR) to Last(Property). Then use that relationship when defining the Value List. You would use values from the new Property TO and Include only related values starting from the new WR TO.

You don't need to change the TO that the existing maintenance request layout uses. Just use that new value list. I believe that will work.