Fields and annotations scales in 2007 vers.

Hello, have you had these problems. I have a block with attributes (with annotations scales) which updates with some block properties. When I save back to ACAD2007 vers (I'm currently use 2011), field looses its properties to update (#####). I thought that in vers 2007 have fields and annotations. We work with consultants with vers 2008 so I have to save back. In my case I use doors and windows with different annotation scales (and I want to scale only the size of numbers). One of the attribute in block is not annotative, but I have asigned annotative properties to particular block (to different scales) I have attached sample.

sample_2010.dwg

P.S. if there is no solution, I just want to preserve people, who use this method from big troubles, which I had. I have #### size on 100 doors and windows in the drawing, because I have set to save in vers.2007 in options.

sample_2007.dwg

AutoCAD 2007 does have a FIELD command. It did not, however, support annotative scaling. That feature became available with AutoCAD 2008.

I am kind of surprised that someone at the "other" firm didn't tell you this.

"I am kind of surprised that someone at the "other" firm didn't tell you this."

That was because I didn't send the files with backdown save. I just put my autocad to save automaticly to 2007, and when I saved 2 files, (two times before I could see that there was trouble, and couldn't restore .bak files) I was awful surprized ... Now before send them files, I use one lisp to change fields to text (R-FIELDS). They use ACAD2008 but the version they could open files is 2007 ... Be careful !!!

So when you do a "saveas" you do not save under a slightly different file name? Ex. Save a 2010 drawing named MyDrawing.dwg to 2007 file format as MyDrawing[2007].dwg.

The thread will became too long unnecesarilly, but I'll explaine, I really want to prevent others from that boredom mistake. I use e-transmit to create new .exe (selfextract .rar )file with all my x-refed files in one folder. In e-transmit options, I have set to save in 2007, purge and so on. But I opened all that files again to look is it all right. So I set to save 2007 vers, to not forget some file and saved them again. Then I have forgotten to restore file version to 2010 and this was the result.

You should not have a problem the way you're doing it. You might also want to turn on the Save Fidelity option in the eTransmit setup dialog - that way the Annotative Scaling generates extra layers for each scale version and VPFreexes accordingly (much like you'd have done prior to AnnoScales). That way at least the laout tabs should look correct in 2007-and older.

I'm surprised that 2008 has issues with the fields. What field-type are you using? Are you linking to something which is new since 2008? Perhaps the object the field references becomes a proxy when saved down to 2007 - i.e. it's properties become unavailable. The only thing I can think of which might do this would be dynamic arrays, but that's only available since 2012 (so it can't be that). And I can't see any field linking to constraints - which are the only other new object types.

Are you using dynamic blocks? I've seen those go screwy when saved back to old versions. If the "size" field links to a door DB's size parameter you might find that the door block has become a flat (non-dynamic) block due to the save down. I don't know why this "sometimes" happen, I can understand if there's something new inside that DB (like constraints) - but I've seen it happen with blocks made in 2008, opened in 2011 and saved down to 2007 .

A work-around I can think of: You might want to look at using a lisp which converts all fields to their normal text before doing the eTransmit - of course saveas to a temporary DWG file before you kill all your fields though. Something like these might suffice:

• http://forums.augi.com/showthread.php?72534-Convert-Field-to-Text-within-Block-Globally
  
• http://www.cadtutor.net/forum/showthread.php?16409-Global-Coversion-of-Fields-to-Text
  
• http://forums.augi.com/showthread.php?138527-Convert-Field-Value-to-String
  

Thanks irneb. I couldn't see Save fidelity option in eTransmit. My SAVEFIDELITY system variable is set to 1. As you see at the samples of the my first post there are dynamic blocks, annotation scales and fields. The interesting thing is that if signs and marks, which are annotative at all haven't these problems, but when annotative properties has assigh inside of the block - boom ####. May be this "dirty" combination is killer to vers. 2007. I use other lisp (even I don't know who has written it) "r-fields" to kill fields, and it works very well for attributes, text and mtext but only in model space. I have fields in my layouts but nothing important. It also not kills fields in tables. I'd looked at your links - I've seen that it's lisps for killing fields properties, but I haven't time for now to look if they work for this later I'll check. (I count the word "kill" - this post became like triller )

P.S. I've seen it. A tick under file format version in eTransmit, but it is checked.