First, Thank you for all the assitance you have provided for all my other projects.. I visit your site OFTEN, and am more than mildly impressed with your work.
Thank you DIW, I appreciate your gratitude & compliments
The hope of this, is to minimize us opening and closing of files when/if the dwg's name is changed by the engineer. I.E. Instead of opening 60 DWG's to perform the change, we just change the number in Windows Explorer. As well as for use in our template drawing, so this can be automated on newly created DWG's. This would be especially handy when copying drawings from older project to newer projects and renaiming. So, I would definitly prefere some form of Field Expression, and or DIESEL code. With the use of the LSP it will still require opening the drawing and performing a function, and the lisp would have to be installed on ever CAD technicians machine, both here and in KC. This could be problematic to coordinate/educate CAD technicians. The Field Expresson and Diesel code would be much cleaner operationally across the board. Although, from the results of my searching, seemingly much more difficult.
Do you think this is impossible with Field Expressions or DIESEL .. or even Rtext?
Regarding the possibility of using Fields (which includes DIESEL):
- If the hyphens in the filename were commas -> yes.
- If the sections of the filename were of fixed length -> yes.
Otherwise, I would say no, since DIESEL does not offer a means of reporting the position of a character in a string.
Regarding the LISP solution:
With the use of the LSP it will still require opening the drawing and performing a function
Firstly, note that a solution using fields would still require you to open each drawing in order to update the attribute fields (that is, the field will only be 'recalculated' when the drawing is next opened).
However, a LISP solution would operate in an identical manner - you would simply include the above code in an acaddoc.lsp saved to a network support path and the code would automatically run on drawing startup to update the necessary attribute values - there would be no user input required, only an initial setup.