Word XP Template modification problem

[MTarkington]

I have a customized template to which I have added more pages.

It contains a macro that allows the user to enter a name and client number, and will then populate this field throughout the document.

The problem is that when the template is opened (to create a new document), after the macro is run, the cursor shows up on the 4th page. I cannot find a way to make the cursor show up on page 1, or anywhere other than the top of page 4.

I'm sure there's some sort of formatting issue, or a setting that I've missed, but I can't find it.

Any help would be appreciated.

Thanks,
Mark

 

[Phaed]

u r using form fields? if so, doc is protected?

other than that...more details needed

 

[MTarkington]

The form is not locked, it will allow changes to the template.

When the template is opened to create a new document, you get a screen requesting client name and number.

After entering the name and number, you click enter and the template is populated with that data where it is supposed to be.

Before modifying the template, when the data was entered and enter was clicked, the cursor would show up in the first field of the document, ready for input.

Now, after modifying, once the data is entered and the enter clicked, the cursor shows up on page 4, in the heading.

This template is for our end-users, therefore, I am trying to make the modifications as painless as possible. The cursor showing up on the 4th page is not helping.

Hope this helps...

Thanks again,
Mark

 

[Phaed]

with no offense intended, please try and use terms properly. much easier to figure out what is happening.

1. "forms is not locked, it allows changes to the template"

bad statement. A template should NEVER, EVER, be changed by a user. A template should NEVER, EVER, be even opened by a user. a template creates a clone of itself, a new document and that is done with File, New. if user are acting on this file any other way, then template is not being used correctly.

assuming that you really mean the form is not locked and allows changes to the FILE created from the template. but if NOT locked, then forms (at least form fields do NOT work. confused.

2. the cloned file (from the template NOT the "template opened"...hopefully) open a VBA procedure runs a dialog box. User enter info.

3. the cloned file (again, hopefully NOT the "template file") is populated with dat "where it is supposed to be. Where? How? by bookmarks? by Form fields, by Activex controls. U state form is NOT locked? what u means by "form? but if gong where supposed to be, that good.

4."Before modifying the template (BAD BAD BAD), when the data was entered and enter was clicked, the cursor would show up in the first field of the document, ready for input." if the form IS locked cursor will go to first field for enter., yet u state form is NOT locked. confused. if u r using a UserForm to get initial data, WHERE r u putting results of UserForm??? If location is a formfield, then cursor will go to to last place u inserted the data.

PLUS if U[/U} are putting the dat from the UserForm into the fields, why do u want the cursor there anyway? no need for user input AGAIN, as they already did it from the UserForm. confused....seem there is duplication.

5. "the cursor shows up on page 4, in the heading." this is details need. "page 4" means nothing to me. what is different about page 4?? Who knows??? Did u make a section break that is now protected. is document protected for forms or not? u state NOT locked, but is acting as if it is.

please answer..
a) does page 4 have a form field? r u even using form fields?

b) does page 4 have a section break before it?

suggestions: if u want 2 locate cursor anywhere, if it IS protected, unprotect doc first, move cursor, then protect again. a protected for forms doc will only allow cursor in unprotected sections. it will NOT allow cursor to even b in protected sections. so if page 1 is protected, then other than actual fields, the cursor will not go there.

if u give a bit more detail this simple 2 figure out. seems a minor change will fix this.