I know I can "lock" the header or footer on the screen in a runtime. Because of the customer needs for this particular solution, however, I need to create and network the db using 4.1. I still need the header to remain still at the top of the screen even when the customer needs to scroll down the body. Any way to do this?

The only way would be to set the layout as a List, rather than a Form. This way the header and footers will stay displayed at all times.

It only has significience when in Browse & Fine mode. The other modes do not have a concept of List vs Form view.

Thanks. I did that. It seems that change is only an option in Browse mode. Any way I can script the file to be in List Mode all the time?

Please tell me there is some way to have the best of both worlds: to be able to scroll down the body AND be able to enter data in the header. I didn't realize that in using List Mode I would have to sacrifice data entry in the header.

Not that I know of...

quote:

---

Originally posted by Allegheny:

Please tell me there is some way to have the best of both worlds: to be able to scroll down the body AND be able to enter data in the header. I didn't realize that in using List Mode I would have to sacrifice data entry in the header.

---

What if you would use a normal header in browse mode, and the 'scrolling' part would be a portal based on some self-relation? Or am I overseeing something?

quote:

---

Originally posted by Allegheny:

Please tell me there is some way to have the best of both worlds: to be able to scroll down the body AND be able to enter data in the header. I didn't realize that in using List Mode I would have to sacrifice data entry in the header.

---

What if you would use a normal header in browse mode, and the 'scrolling' part would be a portal based on some self-relation? Or am I overseeing something?

I had to solve this problem myself. I did it by creating global fields for the information I wanted to appear in the header. I had the user fill in the data, like the date of the report and individual whose records were going to appear on the list. Then I used Merge Fields and put them into the heading. Whatever data was in the fields, appeared in the header.

It seems to work!

When I first tried it, I did not use global fields for the header information. In that case, as you click from record to record in your "list" the information changes depending on what is in the fields on the different records.

In some cases this is handy because if you are always going to be say finding a group of customers from a particular city, you can do a find and since all the city fields have the same info, the header will indicate the right city. In this case the field doesn't have to be a global field.

Hope this helps you. It sure helped me when I was baffled abouthow to accomplish what I wanted to do.

Bev

GibCo