Fix Word PullAutoText Error in Legacy Drop-Down Form Fields
Question details
Resolve a Microsoft Word PullAutoText error that appears after editing entries in legacy drop-down form fields.

- Product
- Microsoft Word VBA template with legacy drop-down form fields
- Device & OS
- not provided
- Scenario
- The user is editing a Word form that uses legacy drop-down fields and a VBA procedure to insert AutoText entries based on form-field results.
- Observed behavior
- After entries in legacy drop-down fields are edited, the form triggers a PullAutoText error and the AutoText insertion fails or is interrupted.
Make a copy of the affected Microsoft Word template and open it with the Developer tab enabled. Check that you can access both the VBA editor and the AutoText entries referenced by the form.
Test the Template Copy and Review the VBA AutoText Logic
Use this first to isolate whether the error comes from the VBA code, the legacy form-field names, or the AutoText entries themselves.
The VBA procedure likely depends on the bookmark names of legacy form fields and the template's AutoText collection. Editing drop-down field results changes the stored field value, so a mismatch in the code can trigger PullAutoText.
Open the original template in Microsoft Word, go to File > Save As, and save a copy with a new name before making any changes.
Press Alt+F11 to open the Microsoft Visual Basic for Applications editor and locate the module or procedure that runs the AutoText insertion.
Confirm that each form-field bookmark referenced in the code exists in the document and that each AutoText entry name used in the code is still available in the template.
Protect the form for filling in, change each legacy drop-down field, and note which field choice triggers the PullAutoText error.

Convert Legacy Drop-Down Fields to Content Controls
Use this for a longer-term fix because content controls are more reliable than legacy form fields and reduce fragile form-field dependency.
Share a Sanitized Template for VBA Programming Review
Use this when the VBA logic is still unclear and a programming expert needs to inspect the actual template.
Use WPS Writer as a Free Alternative for Word Form Templates
If the PullAutoText error is tied to fragile Microsoft Word VBA and legacy form fields, WPS Office is a free, lightweight alternative. WPS Writer opens Word files, supports familiar form creation, and helps you rebuild forms in a Word-compatible format without depending on complex AutoText VBA.
- 1. Download WPS Office: Go to the official WPS Office download page and install WPS Office on your Windows or macOS device.
- 2. Open the Word template in WPS Writer: Launch WPS Writer, click File > Open, and select your existing .doc or .docx form template.
- 3. Rebuild or adjust drop-down fields: Use the form controls available in WPS Writer to recreate the drop-down lists and avoid the legacy macro dependency.
- 4. Save in Word-compatible format: Click File > Save As and choose .docx or .doc to keep the template readable in Microsoft Word.

Frequently Asked Questions
What causes the PullAutoText error when a legacy drop-down field is edited?
The error usually means the VBA procedure is trying to insert an AutoText entry by name or use a form-field result that no longer matches the current template. Check the bookmark names, the available AutoText entries, and the code's assumptions in the VBA editor.
Can WPS Office repair my existing Word VBA PullAutoText procedure?
WPS Writer is not a VBA repair tool for Microsoft Word. It can open your Word template and is a free alternative for recreating the form, but complex Word AutoText VBA generally needs to be tested or rewritten in Microsoft Word.
How do I convert legacy drop-down form fields to content controls?
In Word, enable the Developer tab, select the legacy drop-down field, delete it, then use Developer > Controls > Drop-Down List Content Control to create the replacement. After that, update any VBA references to use content controls instead of FormFields.
Do I need to share the original template to get help?
No. Create a copy, remove confidential information and use =RAND() for sample text, save it to OneDrive or Dropbox, and share a view-only link so other people can inspect the VBA safely.
Will disabling macros stop the PullAutoText error?
Disabling macros can stop the procedure from running, but it also disables the AutoText automation. It is better to review the VBA code in a copy or convert the form fields to a more reliable method.




