I inherited a database that, in addition to other fields, contains a numeric field identifying a meeting and fields describing services generated from that meeting. The problem is one meeting might generate one service or five and each service is denoted in a separate record - with the same meeting number. is there a manageable way to deal with this data so I can see in a layout one meeting (number) and all the services associated with it?

Thanks,

Rick

You really haven't made the previous structure clear.. Are the services already stored in a seperate table providing one record for each service, or are they stored in the meeting table in fields describing the services?

Either way the correct structure should have multiple services records for each meeting record:

Meeting table -< Services Table

MeetingID...........MeetingID

MeetingDetails....ServiceID

...........................ServiceDescription

Then to view all the services in the services table, add a portal on the meeting layout to the services table.

Sorry for being vague....the services are already stored in a separate table providing one record for each service.

No need to appologize, just kind of hard to answer the question if we're not sure what it is

See if the attached example file helps.

relatedExample.zip

That works wonderfully - thanks! I was envisioning some convoluted Case calculation or other complicated solution. This works!

Rick

No worries .

Add a scroll bar to your portal and you've got unlimited services