2002 Question

[Marc Clamage]

I'm doing some drafting for a client in ADT 2002. I have a drawing (Drawing
1) xreffed into a second drawing (Drawing 2), which is then xreffed into the
drawing with the title blocks (Drawing 3). The problem is that if I don't
open the drawings in that precise order--Drawing 1, then 2, then 3-- I get
an error message saying that the drawing is already in use and do I want to
open it as read only? I'm running 2004 myself and the problem doesn't arise,
but I recall this problem from a couple of years back, and know that there's
a variable or toggle I can set to get rid of the problem. Anyone know the
answer off hand?

Thanks

Marc Clamage
www.emasary.com

[R.K. McSwain]

On 11/9/2004 11:01 AM Marc Clamage wrote:

I'm doing some drafting for a client in ADT 2002. I have a drawing (Drawing
1) xreffed into a second drawing (Drawing 2), which is then xreffed into the
drawing with the title blocks (Drawing 3). The problem is that if I don't
open the drawings in that precise order--Drawing 1, then 2, then 3-- I get
an error message saying that the drawing is already in use and do I want to
open it as read only? I'm running 2004 myself and the problem doesn't arise,
but I recall this problem from a couple of years back, and know that there's
a variable or toggle I can set to get rid of the problem. Anyone know the
answer off hand?

Try setting XLOADCTL = 0

[Marc Clamage]

Thanks R.K., that did the trick!

"R.K. McSwain" <not@autodesk.com> wrote in message
news:gIdkd.18664$bP2.16250@newssvr12.news.prodigy. com...

On 11/9/2004 11:01 AM Marc Clamage wrote:
I'm doing some drafting for a client in ADT 2002. I have a drawing
(Drawing 1) xreffed into a second drawing (Drawing 2), which is then
xreffed into the drawing with the title blocks (Drawing 3). The problem
is that if I don't open the drawings in that precise order--Drawing 1,
then 2, then 3-- I get an error message saying that the drawing is
already in use and do I want to open it as read only? I'm running 2004
myself and the problem doesn't arise, but I recall this problem from a
couple of years back, and know that there's a variable or toggle I can
set to get rid of the problem. Anyone know the answer off hand?

Try setting XLOADCTL = 0