Page Header start page

[JuniorWoodchuck24]

Is there a way to make the Page Header start on a certain page and go from that point forward?

My Report Header is a bit long and goes into two pages and I want my Detail to come in at the middle of the page not my Page Header. So is there a way you can make it Report Header-Detail-Resume Page Header on 3rd Page-Detail?

 

[namliam]

In the report properties under format you have a few options to set the Page header
All Pages
Not with Rpt Hdr
Not with Rpt Ftr
Not with Rpt Hdr/Ftr

See if one of those are what you are looking for...

 

[JuniorWoodchuck24]

That took care of it. Thanks.

Was going to ask a question on concatenating as well. When you pull in a Field from a table can you add a string to it?

For example:
Add existing field car
Pulls in car and then add extra text:
Ford
Ford - 2007

so Ford would be in the field and "- 2007" would be the string

 

[namliam]

Sure, but if you add a string it will be the same for all in the report any concatination is something like:

"Text" & " is " & "concatinated"

Resulting (obviously) in:
text is concatinated

 

[JuniorWoodchuck24]

I'm familiar with the & making two things placed together and I can make it concatenate if I run a query from the table and do it there. My problem is within the report when I'm pulling fields from a table how to concatenate two fields. The reason they're not together in the first place is due to the fact of how they are needed. So if I had a table of vehicles:

Make (Field1)
Ford
Toyota
Honda
Chevy

Build (Field2)
Mustang
150
350
Focus

and so on. When I add existing fields into a report I'd like to conatenate Field 1 and Field 2. Now in a query all I do is [Field1] & "-" & [Field2]. This doesn't work in the controlsource for a text box in the report. I'm thinking my syntax is in error.

 

[namliam]

Your syntax is not "in error"

In a control source you simply have to put a = in front:
= [Field1] & "-" & [Field2]

However it is also quite possible to "simply" add a field to your query that already does this in the query rather than the report, in which case you circumvent this problem completely