Adding Content Controls to your form is the easy part. This means you can write the variable data once and then the relevant CCs appear wherever they are needed. I think it is a lot easier to hold all the ‘forms’ in the same document. I also haven’t seen yet how to insert one item, say Case name into multiple places in the document? Personally I prefer a VBA userform, but I don’t know enough about contentcontrols to be make a informed decision? I have taken a good look at Greg Maveys site, he explains a lot about contentcontrols, and it seems as if you don’t need a VBA userform – it looks like most of the time he enters straight into the document? No problem with backward compatability so will use contentcontrol.Īre you saying it would be easier to have multiple forms/templates within the one document/file? I can live with this if its easy to “jump” to each page for the end user (is this done via building blocks?) You could get creative to stay with a single document and use building blocks to display each of the customised documents on demand – leveraging the same custom xml or document properties. Since you want to save the field entries to multiple output documents then I would guess you can’t really avoid using end-user macros especially if you want subsequent edits to fields to be replicated across documents. Bookmarks are pretty fragile and susceptible to users editing the content without paying attention to the ‘bookmark’ ranges. The DocVariable or alternatively, Custom Document Property methods would be more robust in the case of saving to doc format but it has the drawback of requiring macros to edit the document fields.īookmarks + userform and macros might also work for you but will require a bit of fiddling to find bookmarks and mapping to userform fields when the field needs to appear in multiple locations. The common doc property fields (Insert>Quick Parts>Document Property) allow you to avoid this complexity but you will rapidly run out of fields. However, you will need macros and/or the Content Control Toolkit to do the setup linking the xml fields to each Content Control. The big benefit of the Content Controls is that a userform and macros is an optional extra and may not be necessary for the end users. I personally go the Content Control way now but this functionality will degrade if the document is going to be saved to Doc format. So of the methods listed in the subject line, which is best before I start to get my hands dirty? Plan on starting in Word 2007 but will be on Word 2013 pretty soon.Įach option has a significant drawback so whichever method you choose will have some repercussions. A later stage of the project may do things in the background like sending emails. This data, once edited should update the forms.ģ. So when the form set is reopened, ideally the userform wants to be displayed again, and still be populated with the data that was originally entered. The form set that is created is a bit of a living document, in that after its been created it is saved to a folder on a network share for that “case” and may be opened, data change and then resaved until the case is closed. A userform that prompts for a variety of data, and then populates several documents (we call these documents a “form set” – there is a form set created for each “case”).Ģ. I want to do something similar again, but I understand that times have changed, and my requirements this time are slightly different:ġ. Nothing too special about that, and many years ago I did it with bookmarks. I have a userform and want to put the data from that form into about 5 different documents.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |