changing page setups

[tomcarver]

Hi,
I use acad r2008. I thought I had my page setups under control untill a few weeks ago. The 2 main setups I use are to plot directly to the printer and to plot to a file so I can send a batch to make collated sets. All of a sudden, some of the drawing files have their page setup portrait/landscape check box reversed from what it was. The weird thing is, not all of the files are affected. This happened after the hard drive failed on our Oce' printer and had to be repaired. Anyhow, is there a global way to apply page setup changes? I'm not using sheet sets.

thanks
Tom Goodman
Wilson, NC

[rkmcswain]

Here (http://lynn.blogs.com/lynn_allens_blog/2006/04/a_hip_tip_from_.html) is one way.

[irneb]

Sorry RK, our gateway blocks that site ... so I don't know if it's actually the same thing.

Or you could try the scripting portion explained in this thread (http://forums.augi.com/showthread.php?t=80461&highlight=mpagesetup). You "shouldn't" really need to use my lisp for this case, but then it couldn't hurt :mrgreen: to update the tabs as well.

[rkmcswain]

Sorry RK, our gateway blocks that siteIt's Lynn Allen's blog - this particular post talks about using DWG Trueconvert (which is now in TrueView) to batch add/update page setups.

[dgorsman]

It's Lynn Allen's blog - this particular post talks about using DWG Trueconvert (which is now in TrueView) to batch add/update page setups.

We've used that method here to reset some old page set-ups with incorrect settings. With the "set default plotter to 'none'" option checked its one of our standard things to do when drawings come in from outside the company.

[irneb]

You know of course you don't need to change the page setups at all. What I generally do is have a set of "Printing Templates" with the various printer / page size / pen settings / etc. combinations as Named Page setups inside ... I can then import them to a Publish job at any time, setting all or selected sheets to a particular Imported Setup at the time of printing. This also works across multiple DWG's & Tabs ... and you're not modifying the DWG files at all.

[dgorsman]

You know of course you don't need to change the page setups at all. What I generally do is have a set of "Printing Templates" with the various printer / page size / pen settings / etc. combinations as Named Page setups inside ... I can then import them to a Publish job at any time, setting all or selected sheets to a particular Imported Setup at the time of printing. This also works across multiple DWG's & Tabs ... and you're not modifying the DWG files at all.

Yes, and no. We get drawings that come in from outside the company with the current plotter set to something we don't have, same thing with CTB files. When Publish gets to those it typically throws an error and stops the operation. This is as much to put the drawings to a clean state as to assist in plotting.

[irneb]

Yes, and no. We get drawings that come in from outside the company with the current plotter set to something we don't have, same thing with CTB files. When Publish gets to those it typically throws an error and stops the operation. This is as much to put the drawings to a clean state as to assist in plotting.Sounds as if the DWG's are actually faulty. I've never had the publish crash on me yet ... even if the plotter's set to none (or a non-existent) or if the CTB can't be found. It doesn't matter to us how the tabs are set-up, since we very seldom print using the defaults (always use the named page setups or import them from another DWG if they don't exist).

Where we have found problems is if the linework on the tab was not drawn at the correct position. This happens if some dimwit just started drawing wherever and then used Window selection for the plot area. The only "solution" I have in these cases is to have my page setups use Extents instead of Layout ... but then if they also have ancillary items next to the TB (e.g. comments on revisions) this causes an unwanted shift :roll:

But as RK would say, that's a training issue. The problem is fixing 1000's of existing DWGs. That's part of why I have written that routine.

[murrayc.49304]

Try this LISP routine