![]() BuiltInDocumentProperties( "Comments") = sLocationĮnd With 'repaint document to show new values BuiltInDocumentProperties( "Company") = sClientNumber ![]() BuiltInDocumentProperties( "Category") = sReportType BuiltInDocumentProperties( "Subject") = sProjectNumber BuiltInDocumentProperties( "Title") = sProjectTitle ,sReportType As String 'read whats in the controls and assign to variables With MeĮnd With 'set document properties With ActiveDocument '200607 strive4peace Dim sProjectTitle As String _ I didn't find the other properties you mentioned - am using Word 2007 for this to be sure you can open it with 2010, and these are the built-in document properties to pick from: TextBox1 -> ProjectTitle (Title) -> character style = aAllCaps The database property I used is in parentheses. I changed the Name property of the controls on your userform. ![]() When you insert a built-in Document property, it becomes a content control. You'll need to turn the Developer ribbon on to set Properties for the controls. That way, in other places, they won't be changeable - so it just depends on what you want. Define other styles that you might want like aProjectTitle, aProjectNumber, etc. So if you're going to insert text from styles, you probably want to name them specifically. You would insert text from a StyleRef INSTEAD of a bookmark cross-reference or a copy of the document property content control I know this looks pretty rough at this stage but compared to where it was (sections, tables, and appendix manually numbered, manually double spaced between paragraphs), it's incrementally better. I'm not sure my coworkers would remember to change them under File, Properties, Advanced Properties. It also makes more sense in doing a batch of work, rather than one report at a time.Īlso thought about using the general fields within the document (Client, Document Number, Project, Purpose, Reference) but if I could link those to a user form that would make it feasible. But I made something that uses merge to fill out a series of complex tables in Word, and so far only one of the engineers is using it. The other way I would think to do this is using Mail Merge to create then fill in the fields. Location: This will be typically "X County" or "Y City", Florida and appears on the cover and in the header of the letter only.Ĭlient Project No (here noted as FPID No): for some projects this will also go into the footer, but most commonly, like location, cover and letter header only. Report Type: These will generally be Report of Engineering Investigation, or a specific report category - also in all three places with the previous items. Project Number (our internal number): on cover, in header of letter, and in footer throughout, same as above. Project Title (also report title): Bold all caps on cover page, bold all caps in introductory letter, bold italics title case in the footer throughout the document from page ii of a letter (if applicable) through end of report (not appendix.) ![]() The key info that repeats throughout the document: ![]() I took what I have so far of the report template, took off our company references, and grabbed the first several pages. So a lot of bad habits and pesky errors persist. Word is something that I only used for the most basic purposes until a change in jobs (I've used Excel more frequently.) And though I took some online courses, most of my work is doing revisions on existing reports, either made from old templates or from re-edits of old reports. The YT guy's method actually does work for simple purposes, but agreed, I did rename the controls the one other time I used it. Crystal, thank you so much for your thoughts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |