Tab key problem in a protected document containing a VB control

[Elbyron]

Steps to reproduce the problem:
1) Create a document with protected and non-protected sections
2) Create a table in a non-protected section.
3) Protect the document. Note that the tab key advances the cursor to the
next cell in the table, as expected.
4) Unprotect the document and turn on design mode.
5) Add any Visual Basic control anywhere in the document.
6) Turn off design mode and protect the document again. Now try to press tab
in the table - it will jump to the next unprotected section (or back to the
top). Even if you remove the VB control, the tab behavior is still affected.

I tried overriding the tab key behavior by creating a macro named NextCell,
but I found that once you add the VB control it no longer calls this function
- it's doing something else. I couldn't find anything on Microsoft's support
site about this issue, and couldn't find a solution via google searching
either.

This problem is very annoying as I could benefit from being able to use VB
controls in a protected document. But if the users can't navigate the table
as usual (especially tabbing past the end to create new rows), I have to find
workarounds using macros and toolbar buttons.

I am using Word 2000, so maybe the problem was fixed in a later version. I'm
rather doubtful, but please let me know if it works in your version so at
least I know I can use VB controls in the future (if we ever get around to
upgrading). Any suggestions for workarounds are also appreciated.

Thanks,
Elbyron

 

[Doug Robbins - Word MVP]

Not that it is any comfort for you, but the same behaviour occurs in Word
2007.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

 

[Elbyron]

Thanks Doug. I tried it at home and found that the problem also exists in
Word 2003. So it would be reasonable to assume that it happens in all
existing versions. Would there be any point in reporting this to Microsoft?
Would they even consider it to be a bug?

 

[Doug Robbins - Word MVP]

I would say that it is a bug, but as in Word 2007, formfields are being
deprecated to Legacy controls in favour of the use of Content Controls,
which do not require a document to be protected for forms, it is almost
certain that nothing would be done about it.

Nonetheless, I will report it.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP