As with their predecessor form fields, they can be purposed for form data entry (i.e., places where you want your form users to provide data).
Version 3.4Ĭorrects data fields conflict errors when batch processing files. Processes extraction to Excel when the form field count exceeds 255 using an instance of Excel (vice ADODB connection). Version 3.3Įxcludes Access as a target data storage file if the form field count exceeds 255. Resolved an issued encountered when the utility attempted to write individual field data to an Excel worksheet when the length of the data string exceeded 255 characters. Therefore the use and need of content controls for purposes other than form data entry is minimized. I have become convinced that the editing restriction "No Changes (Read Only) with exceptions (editors) is the most effective and robust method for using content controls in forms. Version 3.1 shifts the emphasis from tagging (to process) content controls purposed for form data fields to tagging (to filter and exclude) content controls that perform other roles (e.g., a rich text control used to group boiler plate text and form data fields).
#Text form field word 2013 in vba update
I did not take the time to update every image so you may see some minor differences between the dialogs shown here and the dialogs in the actual add-in. Note: One or more images in this tips page may still reflect version 2.0. We have upgraded of the title\tag utility to support naming formfields and created a new utility to convert formfields to content controls. Like most projects that Graham and I collaborate on, the capabilities of version 3.0 expanded significantly beyond just using ADODB for Excel. I had been using the ADODB\SQL method for data extraction to Access in my version 2.0 and immediately saw the benefit of using it for Excel also.
Version 3.0 started life after Graham proposed using the ADODB engine and SQL to write the extracted data to Excel. I have left them posted on this site so visitors can study and reference the VBA code. This add-in refines and further develops many of the techniques I used in those. I have previously published other template add-ins to facilitate data extraction including Extract Batch Form Data and Extract Data from Word Document File. It compliments a similar add-in, Word add-in to extract data from protected forms developed and published by my long time friend and frequent collaborator Graham Mayor. The add-in was developed in Word 2010 but tested and applicable to Word versions 2007/2010/2013/2016.