Position of section break on page 1

[Robie]

Hi

My template has a front cover, which is *all* in the 'header' of the 1st page (which is also section 1 of the template). The front cover takes up the full page as it has backdrop with changeable triangles and some text.

The question I have is that the section break for the 1st page is at the *bottom* of the page even though there is no other text on the front cover apart from the 'header'.

Can someone explain how I can sort this out so that the section break fall on the top of the page & therefore leave my cursor on it when a document is created/opened. Basically, users are complaining that when a document is created, it doesn't show the first page at it goes to the section break at the end of the page.

frontcover.png

Thanks.

Robie

[HansV]

The shapes in the header probably have "Wrap Text" set to Square or Tight. Try setting it to Behind Text.

[Robie]

The shapes in the header probably have "Wrap Text" set to Square or Tight. Try setting it to Behind Text.

Yes, you are correct. Two shapes have a Tight settings. Unfortunately, can't do anything about it at the moment - short of time. It works fine so don't want to change it now - will look into for future.

In the mean time, trying to cheart it by trying to do is go to first page and then move up a screen at a time. Anyway, I am trying to put a pause inbetween each move up but it seems that the 'ontime' function does not work. It just does not pause even if I change 01 to 10. The dummyfunc is an emptry function.

Code: Select all

Function CrappyWay2GotoTopOf1stPage()
'
'   CrappyWay2GotoTopOf1stPage Macro
'
    Application.ScreenUpdating = False
    Application.OnTime When:=Now + TimeValue("00:00:01"), Name:="dummyfunc"
    Selection.MoveUp Unit:=wdScreen, Count:=1
    Application.OnTime When:=Now + TimeValue("00:00:01"), Name:="dummyfunc"
    Selection.MoveUp Unit:=wdScreen, Count:=1
    Application.ScreenUpdating = True
    Application.ScreenRefresh
End Function

[HansV]

Put the line

Selection.MoveUp Unit:=wdScreen, Count:=1

in the dummyfunc function instead of in the calling function. Application.OnTime does not make the calling function wait! It merely schedules some other code to be executed at the specified time.

[Robie]

Put the line

Selection.MoveUp Unit:=wdScreen, Count:=1

in the dummyfunc function instead of in the calling function. Application.OnTime does not make the calling function wait! It merely schedules some other code to be executed at the specified time.

Thansk Hans.

Did as you suggested but now it seems it doesn't even call the 'dummyfunc' anymore.

Code: Select all

Function CrappyWay2GotoTopOf1stPage()
'
' CrappyWay2GotoTopOf1stPageMacro
'
    Application.ScreenUpdating = False
    Application.OnTime When:=Now + TimeValue("00:00:01"), Name:="dummyfunc"
'    Selection.MoveUp Unit:=wdScreen, Count:=1
    Application.OnTime When:=Now + TimeValue("00:00:01"), Name:="dummyfunc"
'    Selection.MoveUp Unit:=wdScreen, Count:=1
    Application.ScreenUpdating = True
    Application.ScreenRefresh
End Function

Function dummyfunc()
    Selection.MoveUp Unit:=wdScreen, Count:=1
    MsgBox "dummyfunc"
End Function

[HansV]

What happens if you put a statement

Debug.Print "Hell World"

or

MsgBox "Hello World"

in dummyfunc?

[Robie]

What happens if you put a statement

Debug.Print "Hell World"

or

MsgBox "Hello World"

in dummyfunc?

Hi Hans

I have put a msgbox in the dummyfunc already, i.e. msgbox ("dummyfunc"). Weird.

[HansV]

Are you sure that CrappyWay2GotoTopOf1stPage is run?

Wouldn't it be easier to change the Wrap Text property of the shapes in the template(s)? That way, at least new documents would behave better.

[Robie]

Are you sure that CrappyWay2GotoTopOf1stPage is run?

Wouldn't it be easier to change the Wrap Text property of the shapes in the template(s)? That way, at least new documents would behave better.

Ok. Thanks Hans. Let me look into changing the Wrap Text property.