change space alters the Z....

i use this command quite a lot to draw out the viewport with a polyline and change spacing it to model so i know the extent of the viewport box for my anotation....

i just noticed the other day (and i would imagine it's been always doing this) is that any entity that i change space with has the z value change from zero...

for example when i change space form paper to model the polyline, or line, or cirlce, has a z= 5'-11 15/64" and when from model to paper it's -1 31/64" when the original entites are at z=0...

afaik everything is set to elevation = 0 and even "repalce z vlaue to current elevation" seem to have no effect...

any ideas?..a bug in the architecture 2008 lisp routine?..i suppose i could alway replace it with another lisp routine out there but am curious if anyone else can replicate this phenomenum...

I just tried it, drew a rectangle and line in PS at Z=0; Chspace to MS, both still Z=0

ok..so something gone wonky with the lisp then...thanks...

humm, just tried it in acad 2009 and it still does the same...however it still does the same in teh same file...if new, z stays at zero...so there's something up with some of my cad files...i ran an audit, fixed the errors, closed the file, opened it again but the probelm still persist...i wonder if there's some sort a variable that causing this or maybe the problem is deeper then that...

oh well, it's not hard to change the z value after the fact... just thought it's a curious bug...

some new discoveries...

it would appear the probelm starts with our default template file...the first three paper space tabs already have viewport so any changespace commands keeps the enties at z=0...however if i create a new paper space tab anything changesapce command used in that tab will give be the z=5'-11 15/64" issue...

now, also if i copy an offending viewport to a paperspace tab that i know keeps the z at zero, the pasted viewport will continue the z=5'-11 15/64" (71.2352 units) quirk while the existing viewport will stay at zero...

what an odd behaviour...so at least i've narrowed it down to the actual viewport entity that's causing the problem...the only problem is that i can't create a new one to replace the old beacause it will be infected with the same issue...

seems like i'm talking to myself here but hey, does it make good reading for you?..lol...