Strange field action in protected document

[Ken Allen]

We have developed a protected 'form' document that contains what is
basically a description of changes to a test web site that need to be
reviewed. The document is structured with indentation and font styles to
highlight information. The original document, as prepared by the web site
team, contains embedded HYPERLINK fields to provide direct access to the
test site.

In order to tuen this into a form, we replace a special character sequence
into a drop-down with an edit fiedd to permit the user to indicate whether
the change is approved or rejected and, if rejected, to explain the reasons.
The HYPERLINKS are embedded within a MacroButton field to permit them to be
invoked from within the protected form. An example is shown below.

{ MacroButton "FollowLink"{ HYPERLINK
http://a.b.c.d/TestSite/Page.html } }

Of course, the file also contains a macro named FollowLink that contains the
code

Selection.Hyperlinks(1).Follow

Normally, this type of field is the first thing on a line of a list with
special bullet characters and there is text after the field. In most cases
these fields work just fine, simply requiring that the user double-click on
the field to cause the specified web page to be displayed in a browser.

In one case, however, simply clicking once causes the page to move so that
the selected field is in the top 1/3 of the page. Once it is there,
double-clicking will then work. As long as that field is in the top 1/3 of
the page, this behavior is not exhibited.

There are also some of these fields at the end of the document that cause
the docuemnt to scroll to a location near the top of the document (I believe
that the first drop-down field is being selected) when they are clicked.
Since the document is several pages long, this makes it impossible to
double-click on these fields. The only thing different about these fields
that I can see is that there is no text after them; but even if I add some
text they behave the same way.

All of the other fields so defined behave as expected. They do not
reposition the visible portion of the document and a double-click functions
properly.

Does anyone have any idea why this may be happening and what I can do to
stop it?

-Ken

 

[Word Heretic]

G'day "Ken Allen" <[email protected]>,

maybe their security settings???

We have developed a protected 'form' document that contains what is
basically a description of changes to a test web site that need to be
reviewed. The document is structured with indentation and font styles to
highlight information. The original document, as prepared by the web site
team, contains embedded HYPERLINK fields to provide direct access to the
test site.

In order to tuen this into a form, we replace a special character sequence
into a drop-down with an edit fiedd to permit the user to indicate whether
the change is approved or rejected and, if rejected, to explain the reasons.
The HYPERLINKS are embedded within a MacroButton field to permit them to be
invoked from within the protected form. An example is shown below.

{ MacroButton "FollowLink"{ HYPERLINK
http://a.b.c.d/TestSite/Page.html } }

Of course, the file also contains a macro named FollowLink that contains the
code

Selection.Hyperlinks(1).Follow

Normally, this type of field is the first thing on a line of a list with
special bullet characters and there is text after the field. In most cases
these fields work just fine, simply requiring that the user double-click on
the field to cause the specified web page to be displayed in a browser.

In one case, however, simply clicking once causes the page to move so that
the selected field is in the top 1/3 of the page. Once it is there,
double-clicking will then work. As long as that field is in the top 1/3 of
the page, this behavior is not exhibited.

There are also some of these fields at the end of the document that cause
the docuemnt to scroll to a location near the top of the document (I believe
that the first drop-down field is being selected) when they are clicked.
Since the document is several pages long, this makes it impossible to
double-click on these fields. The only thing different about these fields
that I can see is that there is no text after them; but even if I add some
text they behave the same way.

All of the other fields so defined behave as expected. They do not
reposition the visible portion of the document and a double-click functions
properly.

Does anyone have any idea why this may be happening and what I can do to
stop it?

-Ken

Steve Hudson

Word Heretic, Sydney, Australia
Tricky stuff with Word or words for you.
Email (e-mail address removed)
Products http://www.geocities.com/word_heretic/products.html

Replies offlist may require payment.

 

[Cindy Meister -WordMVP-]

Hi Ken,

The problem comes from the fact that you aren't allowed to put the focus in an
unprotected part of the document. Word will automatically move the focus to
the next enabled field, or unprotected section.

I'd say you need to place a form field (with a default text of a space,
perhaps) somewhere near these macrobutton fields so that the focus can jump
there.

In one case, however, simply clicking once causes the page to move so that
the selected field is in the top 1/3 of the page. Once it is there,
double-clicking will then work. As long as that field is in the top 1/3 of
the page, this behavior is not exhibited.

There are also some of these fields at the end of the document that cause
the docuemnt to scroll to a location near the top of the document (I believe
that the first drop-down field is being selected) when they are clicked.
Since the document is several pages long, this makes it impossible to
double-click on these fields. The only thing different about these fields
that I can see is that there is no text after them; but even if I add some
text they behave the same way.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jan 24 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail