Why can't I do a search in the header area?

I need a layout to show the title of the project and then all the related items to that project. But I don't want to have to show the Project title, with every single record.

The layout is in a column. I have the project title in the header, with all of the records in the body.

Any ideas?

Paul

Hi Paul,

The two possibilities that I can come up with right now are either:

- define a script with a 'Custom Dialog' script step to 'set' the field that's in the header.

Activate the script by defining that field as button, or

- organise your layout so that you can view the related items of a project in a portal.

Actually why Filemaker won't let you enter a field in the header of a list is a mystery to me. Suppose they will add this feature in Filemaker 8.0 or so if enough people enter this in the feature-request department on their website!

regards,

Ernst

ernst said:

Actually why Filemaker won't let you enter a field in the header of a list is a mystery to me.

I think this makes some sense, depending upon the field. A field in a header is actually a field from the first record shown, and a field in a footer is a field from the last record shown. Thus, entering such a field requires entering the first or last record shown. I think they should make it possible to enter global fields, since they apply to all records, but any others requires some sort of link between the header and first record being browsed, and entering it involves the possibility of changing it, which requires an update to the first record's fields. I think some of this logic is why it is possible to enter a header field in form view, since the header only relates to the current record and is somehow linked permanently to its body. I would think they must be using some sort of internally defined relationship even to make fields visible in a header or footer in list mode, and would be curious to find out what that is or how it is done.

Hi,

I agree the kind of find you're about to perform is more likely a Filter than a classic Find.

So a Portal would suit your needs rather than a List Layout.

Another method you could try is having a global field g_Project Title.

Set it to not allow entry and put it right behind another field in the Body Part. Change the color so that the user doesn't get confused.

Display a copy of the Global in the header, and use a button to activate a script.

<Script 1>

Goto Field (g_ProjectTitle).

Fill the global with the text, or attach a value-list to this field if you wish.

Then use another button with script

<Perform Find>

Go to Layout X

Find Mode

Set Field(Project Title, g_Title)

Perform Find

Go to Layout (original)

HTH

>> A field in a header is actually a field from the first record shown,

>> and a field in a footer is a field from the last record shown.

Uhhh? I think fields in the header and footer are from the current record.

So why not let the developer decide if entry is permitted or not? Can be really nice/functional/userfriendly/convenient/whatever....

Regards,

Ernst

Well, feed me garlic and call me Stinky. I could have sworn that was the case. It must have been for subsummary fields or something. Or maybe it was this way in 4.0? I remember being warned not to use fields in a header that aren't consistent throughout the current set. Ahh, I believe that may have been for printed layouts, which do show only the first/last record for each page in the header/footer.

It still seems somewhat logical that linking a header/footer to the body in form view might be less complicated than doing so in list view.

Right you are Ernst.

That leads to a MAJOR ommission in the script I suggested.

<Script 1>

Go to Record (first)

Goto Field (g_ProjectTitle).

Fill the global with the text, or attach a value-list to this field if you wish.

Aren't you going to need to make the layout a form view, too?

Nope.

Check the attachment for a file I posted some time ago.

With some adjustments, it can be used here just for a find on project Title.

The file isn't doing anything. It was just the first idea, but you can attach the script you want to the button.

FindsInHeader.fp5.zip

Nice trick Ugo!

Ernst.

Oh yeah, you said put the field behind a field on the body. My bad. I could have sworn you said header, which would work in form mode.