FYI - Well, I figured it out. The Qleader command was used and associated
with MTEXT. The MTEXT was left blank because they just wanted the leader
only. Then the Leader gets moved to a new location and the association to
the MTEXT doesn't reconnect until the sheet is bound or the MTEXT is moved.
So I wrote a quick lisp below to remove ALL leader association. I still
think it is a bug when the associated leader doesn't reconnect when it is
moved. It does it when the Mtext is moved ...
(defun c:leadfix (/ l ss ent enti entn)
(setq l 0 ss (ssget "X" (list (cons 0 "LEADER") )))
(while (< l (sslength ss)) (setq ent (ssname ss l) enti (entget ent)
entn (reverse (cdr (member (assoc 340 enti) (reverse enti)))))
(entmod entn) (entupd ent) (setq l (1+ l)) )
(princ (strcat "\n" (itoa (sslength ss)) " entities modified.")) (princ) )
"John Spangler" wrote in message
news:39D44F7D437F07346690236E1AF9AD84@in.WebX.maYIadrTaRb...
> I am using ADT3.3 using the QLeader command without hook lines. If you
list
> the Leader entity it says "Hook Line: OFF". When the drawing gets bound
to
> another, Hook Lines on some leader entities mysteriously appear in random
> locations. After binding and exploding and you list the Leader entity it
> says: "Hook Line: ON". Please see the example drawing (zipped) uploaded
> to the FILES group under the same subject.
>
> Is this an AutoCad BUG? Any suggestions on a fix?
>
>