TIA
Penny
This is a piece of cake. Proceed as follows:
1. Open the template (or a document based on the template)
2. Choose Customize on the Tools menu.
3. Click Keyboard . . .
4. Choose a Category of action from the list of categories.
5. Choose an action item from the list of action items (macros, autotext,
commands, etc.).
6. Pull down the list called Save Changes In and select your template.
7. Click Assign.
8. Click Close.
Good luck.
Bill Coan
Penny wrote in message <01bdf5ef$e40eb580$6632a8c0@PENNYMILLER>...
Sub CustomPageUpAndDown()
CustomizationContext = _
Templates(FindTemplateIndex("TemplateName.dot"))
KeyBindings.Add KeyCode:=BuildKeyCode(wdKeyPageUp), _
KeyCategory:=wdKeyCategoryMacro, Command:="PageUpMacro"
KeyBindings.Add KeyCode:=BuildKeyCode(wdKeyPageDown), _
KeyCategory:=wdKeyCategoryMacro, Command:="PageDownMacro"
End Sub
Sub NormalPageUpAndDown()
CustomizationContext = _
Templates(FindTemplateIndex("TemplateName.dot"))
KeyBindings.ClearAll
End Sub
Sub PageUpMacro()
MsgBox "New PageUp function"
End Sub
Sub PageDownMacro()
MsgBox "New PageDown function"
End Sub
Function FindTemplateIndex(strName)
Dim varTemplate As Variant
Dim intX As Integer
intX = 1
For Each varTemplate In Templates
If varTemplate.Name = strName Then
FindTemplateIndex = intX
End If
intX = intX + 1
Next varTemplate
End Function
Bill Coan <wnc...@ezmanual.com> wrote in article
<#SPwYCg9...@uppssnewspub04.moswest.msn.net>...
When I redefined the PageUp key to goto the previous field and the PageDown
key to goto the next field in my table it doesn't follow my macro it wants
to fillin by row (which is a default) not column.
Any suggestions is greatly appreciated.
Penny <cc...@televar.com> wrote in article
<01bdf628$d1154a00$6632a8c0@PENNYMILLER>...
When a document is protected, Word interprets the page up and page down keys
differently than at other times. This question has come up before, and there
is no way I know of to overcome this built-in functionality.
Penny wrote in message <01bdf628$d1154a00$6632a8c0@PENNYMILLER>...
One solution, not necessarily a convenient one, would be to use an "on exit"
macro for each field to move the cursor down each column.
Other than that, the only suggestion I could make would be that you create a
user form, where you have explicit control over things like tab order.
Perhaps someone else can offer a different suggestion.
Bill Coan
Penny wrote in message <01bdf62b$5e782280$6632a8c0@PENNYMILLER>...
>I don't want to be long winded or anything but, let me tell you... I have a
>macro that is designed to control the tabbing order in this template
>(specifically I am controling it in a table because I need to fill it in by
>column not row) this template is protected also.
>
>When I redefined the PageUp key to goto the previous field and the PageDown
>key to goto the next field in my table it doesn't follow my macro it wants
>to fillin by row (which is a default) not column.
>
>Any suggestions is greatly appreciated.
>
>Penny <cc...@televar.com> wrote in article