Lets wrap up this month by reviewing the subject matter and exploring some guidelines for consideration.  In this set of exercises we’ve discussed the basic definition and properties of AutoCAD Fields, how they can be inserted into a drawing using text objects and attributes, implementing Fields into title blocks and with the Sheet Set Manager, using them with drawing objects such as viewports, inside of tables for object data and formulas, and also within dynamic blocks to annotate and/or verify its properties.

There are some limitations to Fields, however.  The list of shortfalls includes lack of spell checking ability, text tools within the Express Tools set, and using Fields within drawing files that may be used by someone with AutoCAD 2004 or earlier (otherwise known as making a “round trip” to a version prior to their existence).  There are also some commands in AutoCAD that assist or hurt Fields.  A short list that I’ve compile is as follows:

BURST – will change Fields in attributes to regular text (but will maintain its value)

TXT2MTXT – will change Fields into regular text

TCASE – when used to convert a Field to all uppercase, will convert Fields into regular text

EXPLODE (X) (XPLODE) – will convert a Field to regular text

Find and Replace – will convert a Field to regular text

Replace Field with Text – this is a shortcut menu option that will do exactly what it says

BLOCK – define a block to not be exploded within the dialog box as this will deter converting Fields to text

ATTDEF – use the Preset option in the dialog box to avoid overriding Fields upon insertion within a block

Lastly, there are some instances when Dtext or Mtext is simply a better option than AutoCAD Fields.  Fields are overkill for simple annotation for labels on a drawing.  Also, Dtext or Mtext is your only option when it comes to external references since Fields won’t communicate with drawing files other than the one it’s inserted into.  Essentially, Fields are a very versatile and powerful AutoCAD feature that can be very effective if used correctly.  It is just necessary to consider the small number of limitations and how users could possibly cause them to fail.