Hopefully I am in the right forum.

A simple, I'm sure relationship/layout problem:

I want to print a repair report on equipment. One table has information on the equipment. The other has the information on the service work. There is a one (equipment) to many (service) relationship. I utilized a key field for equipment and one for service, so equipmentID in equipment table connects to equipmentID field in service.

Layout is to be grouped by item name

The layout is set up selecting

:item name (from equipment table)

date, problem, service company (all from Service table)

The report will not show the related field "item name"

Layout is based on "service"

When I change the "layout based on" to Equipment, th item name displays, but I loose the other data that I was able to see prior.

When in the service data entry form, I utilize a drop down list for the item name and all works well.

What have I missed?

Can you Stuff and attach your problem file?

Here is the file. Sorry I did not think of this prior

Your Item ID is never being set in your Service table. So your relationship is never valid. You cannot use a lookup based on the relationship itself to populate the key field. You need to either set it via script when creating a new service or create a relationship from Service::Item Name to Item 2::Item Name (Item 2 is the default TO name that will be used when you create a second relationship between Service and Item), then change your Item ID in Service to be a lookup based on Item 2::Item ID. This way, whenever a different Item Name is selected in Service, the matching Item ID will auto-fill.

I made the changes that you said to do. Now the reports does have more information, but the froup headder, that is the item name still does not appear.

I did remove the relationship between Item ItemID and Service ItemID

What have I missed?

Are the records sorted by the subsummary field? If they aren't, the subsummary won't appear when you preview or print. BTW, the report should be based on the Service table. There's no need to remove the primary, unique relationship, just add one for the secondary relationship between Service and Item, which will only be used for this lookup feature.