Field Text Locking

[Anonymous]

Hey there...I've been working with the idea of changeing how my agency offers some detail information via our website.  However, one issue I keep running into for maintaining these drawing for internal use is fields that I can't seem to lock.  I can set the FILE NAME field in the main drawings and it works great, however, once that block is inserted into another drawing for use the FILE NAME field takes on the name of that particular drawing.  This is the same with the LAST SAVED DATE field.  I've tried messing around with some sttribute itmes, but I can't get anything to work reliably.

I've attached a sample of one of the details withthe field text at the bottom.

Ideas???

Thanks!

[Anonymous]

• convert fields into text
• update your templates to where you've created your own custom fields in the dwgprops

I'm just spitballing here. Do you need fields in your dwgs since you're looking to make them stop updating?

[Anonymous]

I don't want to totally kill the updating, just when the drawing is inserted as a block.  I would still like the fields to work in the original drawing, but when the drawing is inserted as a block into another drawing (assuming they are not EXPLODED) I would like to keep the field from adopting the information from their new home drawing.

I'm probably lloking for something that just is not possible.  The only reason I;m searching this out is that what tends to happen with our standard details is that over time one field or another isn't updated when someone updates something in the detail drawing, and this makes tracking alomost impossible.

[Anonymous]

I'm not sure if that's completely possible, but perhaps there's another angle to attack this from.


Are you familiar with FIELDEVAL system variable?

Controls how fields are updated. The setting is stored as a bitcode using the sum of the following values:

0 Not updated
1 Updated on open
2 Updated on save
4 Updated on plot
8 Updated on use of eTransmit
16 Updated on regeneration

Note: The Date field is updated by UPDATEFIELD, but it is not updated automatically based on the setting of the FIELDEVAL system variable.

These are specific situations you can set your setting to in order to control when a field updates. You can mix and match any of these just by adding the numbers up (for example: to update when you open and save, enter 3 as your field eval setting because 1+2=3).

[Anonymous]

It's a long shot, but could generate some benificial results.