I guess my argument is that sometimes learning to do old things a new way can be a great time saver. So I have no binding love for AutoCad's associative hatching.
This took a couple hours to sort out during a critical deadline. When the source xref plan was changed, the drawing file's associative hatch started a major corruption, because it could not locate the hatch boundaries (which were changed), and the drawing file could not open. I've had my share of hatching problems with that program - remember version 13? The most recent AutoCad hatch problem I've had was a few months ago, when somebody put an associative hatch on an xref plan background in a drawing file (that is, a plan background was used as a source file). I, too, have worked on AutoCad for over 15 years, and I still do at times.
