There are fairly simple ways of hiding tables in Word, but not if they have formfields. An alternative for a table that has formfields might be to have the table on display but the formfields within it locked so they can only be accessed if whatever condition you select from the dropdown has the appropriate answer selected.

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

I like the idea of hiding information not used more for the fact that it gives a clean appearance. If it's not needed or used I'd rather it just not be there.

So... if it has any kind of form fields the table cannot be hidden? That's a bummer.
Option B... separate forms with and without the unneeded information. :/

Yes, you could do that, too.

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

Had you simply copied tables 9a & 9b, plus the updated code from the document in my last attachment (or if you'd stuck with that document and changed whatever other details might need changing), everything would have worked fine. Part of the editing I did entailed renaming some of the formfields & calculation fields so they would work properly with what you're trying to do.

As for the 'other' option, that is necessarily the last row because of the way the coding works. And, once you reach the limit of 25 entries in the dropdown, the 'other' option disappears - since it would no longer be valid. It might be advisable to tell your users that, if they're likely to need multiple rows with 'other' options, they add the necessary rows before choosing 'other'. That way, subsequent rows won't be pre-populated with the results of 'other' options from previous rows.

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

I'll give that a shot. Thanks.

If you're referring to the attachment from this post, when I use it as is without changing the macro it has a runtime error '5941' when I try to apply it to the location dropdown. In the Drop-Down Form Field Options I set GetTblRow on Entry and OtherMunitions on Exit.

I thought maybe it was because that top table had merged cells but I re-did it without using merged cells and it still has the error.

The attachment to post #39 (https://www.msofficeforums.com/word-...tml#post108097) works fine as is, but you can't simply take the existing OtherMunitions macro, which is designed for Tables 9a & 9b, and expect it to work in an entirely different situation. The existing GetTblRow macro won't cause problems, though, as it's only gathering data. Even so, it's not needed just for inputting another location in your first table.

Try the attached update. Note the addition of an OtherLocation macro.

Attached Files

EXPLOSIVE OPERATIONS DEPARTMENT.docm (47.0 KB, 15 views)

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