View Full Version : FIELDEVAL keeps changing value from DWG to DWG
rgorman
2006-06-19, 02:29 PM
We just switched over to ADT/Vanilla 2007 from 2006 versions.
This is happening to both our ADT seats and Vanilla seats. FIELDEVAL is set to 31. Open a drawing and our 'savedate' and 'login' work fine...maybe. Open the next drawing and our FIELDEVAL is set to 4. Reset the "Field Update Settings" and it will work. Open the next drawing and sometimes it is set correctly, but sometimes not. Very frustrating to have to constantly reset the field settings or update the fields manually. And don't get me going on the "LastSavedBy" field option- that hasn't worked at all since fields were an option.
Is this a bug or quirk or something that's going to aggravate me to no end?
It appears that FIELDEVAL is a drawing variable and not a system variable. It is saved in the drawing. You may need to add a small routine in your ACADDOC.LSP file to automatically set the variable to your desired setting.
(setvar "FIELDEVAL" 31)
For the LastSavedBy, you will need to have the AcSiUI.ARX file loaded for each drawing as well. This provides the appropriate information for the LastSavedBy field.
(arxload "AcSiUI.ARX" NIL)
whdjr
2006-06-19, 02:37 PM
It doesn't fix your problem but could be a workaround for now would be to set that system variable within the acad.lsp file. At the end of the acad.lsp file add (setvar "VARIABLE NAME" VALUE) where "VARIABLE NAME" is the name of the system variable you want to change and VALUE is what you want it to be set too.
rkmcswain
2006-06-19, 02:51 PM
It doesn't fix your problem but could be a workaround for now would be to set that system variable within the acad.lsp file.
That will only work if ACADLSPASDOC is set to 1. The use of "acaddoc.lsp" as suggested above is a better option.
rgorman
2006-06-19, 03:21 PM
Thanks for the quick answers. The FIELDEVAL in the acaddoc file works great. I'm still checking on the other arx thing so I'll let you know about that one.
Thanks for the quick answers. The FIELDEVAL in the acaddoc file works great. I'm still checking on the other arx thing so I'll let you know about that one.
I'm not sure if it needs to be in your ACADDOC.LSP file or it would work in the ACAD.LSP file. I can't remember if it needs to be loaded for each drawing. I wouldn't think so, but I do have it loaded with each drawing.
I'm not sure if it needs to be in your ACADDOC.LSP file or it would work in the ACAD.LSP file. I can't remember if it needs to be loaded for each drawing. I wouldn't think so, but I do have it loaded with each drawing.
It's a drawing variable, so it would need to be done for each drawing. The ACADDOC.LSP would be the preferred place for such an item, or possibly the ACAD2007DOC.LSP file.
It's a drawing variable, so it would need to be done for each drawing. The ACADDOC.LSP would be the preferred place for such an item, or possibly the ACAD2007DOC.LSP file.
I was referring to the ARX file that I mentioned earlier. I wasn't sure if it should be loaded for each drawing (ACADDOC.LSP) or for the session (ACAD.LSP).
For the FIELDEVAL variable, I recommended placing the code into the ACADDOC.LSP file.
Leave the ACAD200XDOC.LSP file alone. You do not want your customizations to be discarded by an update. There are numerous discussions on AUGI on the appropriate uses of the ACADDOC.LSP vs the ACAD200xDOC.LSP files as well as the ACAD.LSP vs. the ACAD200x.LSP files.
Leave the ACAD200XDOC.LSP file alone. You do not want your customizations to be discarded by an update. There are numerous discussions on AUGI on the appropriate uses of the ACADDOC.LSP vs the ACAD200xDOC.LSP files as well as the ACAD.LSP vs. the ACAD200x.LSP files.
If the whole point of this line is to fix something that is a bug in 2007, then it seems that the ACAD2007DOC.LSP file might be the correct place for it...
But to be honest, I don't really understand the problem. It isn't one that I've seen - we leave our FIELDEVAL set to the default 31 all the time, and have no issues.
rkmcswain
2006-06-20, 01:59 AM
If the whole point of this line is to fix something that is a bug in 2007, then it seems that the ACAD2007DOC.LSP file might be the correct place for it...
A) There is no bug. FIELDEVAL is saved in the drawing. It is not saved in the registry or anywhere else. Therefore, if someone wants it to be set to 31 all the time, you need to set it to 31 at least once per drawing. Setting this in the template drawing is the easiest way to do this, but drawings for which you have no control (older versions of drawings or drawings from outside consultants), use of "acaddoc.lsp" is the easiest alternative.
B) The "acad200xdoc.lsp" file is supplied and 'owned' by Autodesk. If you alter it, you risk losing those changes. The file "acaddoc.lsp" is created and 'owned' by the user. Autodesk SP's and upgrades will not overwrite it. As Opie mentioned, this is documented in many places, one of those being http://support.autodesk.com/getdoc.asp?ID=TS21336
Mike.Perry
2006-06-20, 08:32 AM
Hi
If the whole point of this line is to fix something that is a bug in 2007, then it seems that the ACAD2007DOC.LSP file might be the correct place for it...Is there a reason why everything is termed a bug by yourself ?
Please define your meaning of a bug, so I may begin to understand your numerous posts that appear to like throwing out that term...
Please note, I am not being confrontational with the above, I am generally interested in hearing your definition of a bug.
Files shipped with AutoCAD ( reserved for AutoCAD functionality ), should not be altered, unless absolutely necessary / no other alternative is available - in my humble opinion.
Please see HERE and HERE, plus a suitable search (http://forums.augi.com/search.php?) on the forums will turn-up lots more information on this subject.
Have a good one, Mike
Chris.N
2006-06-20, 01:32 PM
i and my coworkers have noticed this behavior as well. We use SSM, and i have the sysvar set to '31' in the template. you'd think that would cover the bases, but we still have spontanious resettings that no-one can explain around here, either. i ended up putting the line in my ACADDOC.lsp file as well.
rgorman
2006-06-21, 03:40 PM
Well, at least I wan't alone in this. I find it odd that the "Field Update Settings" in the Options dialog box is of no use DWG to DWG (it used to be a system setting far as I remember).
As for the 'LastSavedBy' problem, that seems to have been rectified thanks to Opie's heads up about the (arxload "AcSiUI.ARX" NIL) function. It seems to work now. Oh, and I put that in the acaddoc.lsp file as well.
thanks again.
rkmcswain
2006-06-21, 03:56 PM
I find it odd that the "Field Update Settings" in the Options dialog box is of no use DWG to DWG (it used to be a system setting far as I remember).
Not sure what you mean by "is of no use"...?
I don't have 2005 in front of me, but I'm 99% sure that FIELDEVAL has always been saved in the drawing, not as a system setting.
A) There is no bug. FIELDEVAL is saved in the drawing. It is not saved in the registry or anywhere else. Therefore, if someone wants it to be set to 31 all the time, you need to set it to 31 at least once per drawing. Setting this in the template drawing is the easiest way to do this, but drawings for which you have no control (older versions of drawings or drawings from outside consultants), use of "acaddoc.lsp" is the easiest alternative.
B) The "acad200xdoc.lsp" file is supplied and 'owned' by Autodesk. If you alter it, you risk losing those changes. The file "acaddoc.lsp" is created and 'owned' by the user. Autodesk SP's and upgrades will not overwrite it. As Opie mentioned, this is documented in many places, one of those being http://support.autodesk.com/getdoc.asp?ID=TS21336
You are saying the same thing as me.
Where we seem to differ is that you say that one should NEVER edit the ACADxxxxDOC.LSP file. You may have a point. Personally, I have never edited this file myself. I was merely thinking that if you have (or administrate) multiple versions of Autocad, and there is something that would normally go into the ACADDOC.LSP file, but you want it for ONLY 2006, then the ACAD2006DOC.LSP may be a good place for it. But since it can get clobbered by Service Packs, and you can control which version of the ACADDOC.LSP file gets loaded by manipulating directories, it may be best to do as you say, and leave it alone.
But I feel this is rather far from the topic the OP asked about... I now very strongly regret my passing mention of the existence of the ACADxxxxDOC.LSP files...
rkmcswain
2006-06-23, 11:52 AM
I was merely thinking that if you have (or administrate) multiple versions of Autocad, and there is something that would normally go into the ACADDOC.LSP file, but you want it for ONLY 2006, then the ACAD2006DOC.LSP may be a good place for it.
In that case you could have a different top level support path for each version, each containing it's own "acaddoc.lsp" -or- identical paths with one "acaddoc.lsp" containing the appropriate code to load a portion of the file based on the ACAD version.
...one "acaddoc.lsp" containing the appropriate code to load a portion of the file based on the ACAD version.
I would go with this option.
rgorman
2006-06-23, 06:02 PM
Not sure what you mean by "is of no use"...?
I don't have 2005 in front of me, but I'm 99% sure that FIELDEVAL has always been saved in the drawing, not as a system setting.
The fact that just about everything ELSE in the Options dialog box is a system setting, isn't it?
Why have the "Field Update Settings" button as a per DWG setting only? That would seem to be a setting that should apply to all your dwgs.
The fact that just about everything ELSE in the Options dialog box is a system setting, isn't it?
Why have the "Field Update Settings" button as a per DWG setting only? That would seem to be a setting that should apply to all your dwgs.
Some drawings you do not necessarilty want the fields to update automatically and some you do. I feel that the current setup of the FIELDEVAL variable is correctly associated to the drawing.
rkmcswain
2006-06-23, 07:06 PM
The fact that just about everything ELSE in the Options dialog box is a system setting, isn't it?
I don't think the OPTIONS dialog has anything to do with the issue. There are ±613 system variables, some are saved in the drawing, some are saved in the registry, and others are not saved at all. Your statement may be true, but I don't think was any intent to put only certain types in OPTIONS. In fact, *most* sysvars that are saved in the drawing, that are also controlled in OPTIONS have the little DWG icon next to them. Why this was omitted for FIELDEVAL is anyone's guess.
Why have the "Field Update Settings" button as a per DWG setting only? That would seem to be a setting that should apply to all your dwgs.
I would disagree, but I may be in the minority also... :?:
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.