I have built a protected form in Word 2007 but the eventual user wants the facility to extend the number of rows themselves in certain tables as the 'standard' amout I have set out may not be sufficient for their needs which can vary from form to form. I knew I would have to utilise a macro to do this but this is new territory for me so I did some Googling and found a suitable macro script on another forum (see script at end of this post). I tested this out on a dummy document using a keyboard shortcut and it worked fine but when I use the macro on the proper form I get a Runtime error, even though the macro does add the extra row. The proper form is not complex as it only consists of the normal protection with unprotected text fields although it is around 10 pages in length. There are no other macros that might cause a conflict.
When I check the debug info, the line oFld(i).Result = "" is highlighted as being the problem.
I have added the error and debug info below, along with the macro script.
Hoping someone can shed some light on this for me.

================================================== =========================

Sub AddARow()


Dim i As Integer
Dim bProtected As Boolean
Dim sNewRow As String
Dim oFld As FormFields
sNewRow = InputBox("Insert New Row", "New Row", "No")
If Left(UCase(sNewRow), 1) <> "N" Then
'Unprotect the file
If ActiveDocument.ProtectionType <> wdNoProtection Then
bProtected = True
ActiveDocument.Unprotect Password:=""
End If
With Selection
.SelectRow
.Copy
.Paste
.SelectRow
Set oFld = Selection.Range.FormFields
For i = 1 To oFld.Count
oFld(i).Result = ""
Next
End With
If bProtected = True Then
ActiveDocument.Protect _
Type:=wdAllowOnlyFormFields, NoReset:=True, Password:=""
End If
End If
End Sub

Attached Images

	macro_error_1a.jpg (20.0 KB, 11 views)
	macro_error_1.jpg (84.2 KB, 11 views)

Hi Frank,

Does the row you're actually adding contain formfields and, if so, what kind of formfields are they?

You might also look at the discussions at:
http://www.tech-archive.net/Archive/.../msg00682.html
and:
http://www.eggheadcafe.com/microsoft...ted-table.aspx

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Paul - thanks for the answer which I wasn't able to respond to yesterday.

I've had another look at the form and did some further testing. The error only appears when trying to add a row to one particular table in the form. This table has three coulmns with normal text-only form fields but a fourth column has a drop-down box option in each row so presumably it is this which is causing the problem?

Things have moved on a bit from my original problem. I dispensed with the dropdown option in the table which gets rid of the RunTime error but I now have the problem of macro disabling/enabling. I was totally oblivious to Microsoft's security stance on macros as I successfully did all the macro testing on my own PC but, of course, as soon as I send the form to another person their copy of Word blocks all macros and I have discovered that even if they select the option to run macros it still won't work on their PC. Even if the macro were to work via this option I feel this is kind of defeating the purpose of having the macro in the first place as the plan was to allow staff, who may not be especially familiar with Word anyway, the simplest way of adding additional rows to the form.

Hi Frank,

For security reasons, there is no way to enforce the running of a macro. Nevertheless, if the form recipient enables macros on their PC (installation of the vba components as part of Word's setup can be denied) and allows it to run, I can see no reason why the code shouldn't run on just one PC.

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Thanks Paul. Since my last post the manager who requested the form has seen a PDF example in use with another company that has 'sexy' Add and Delete Row buttons and she wants me to create one like that!
It would be done in Adobe Live Cycle Designer, which I do have as part of Acrobat Professional, but I just need to go away and learn how to use it now.

Thanks for your help anyway.