Publish Command via script

[mrfilly]

We are using a mixture of ACAD 2012 & LT2012. The command '-PUBLISH' is recognised in ACAD2012, but not in LT2012. Therefore several scripts that we have, to publish a .dsd file, do not function on the LT2012 machines.

What are the alternatives?

The end scenario is to be able to create a multi-sheet pdf file, from an .dsd file (that is automatically created via excel), by using a combination of .bat and .scr files - without user intervention.

NB: The .dsd file contains a list of page set-ups that are various views within a single .dwg file.

[pendean · Accepted solution]

It's just not available in LT: there is no workaround.

[mrfilly]

Hi Dean,

Thanks for a quick response.

Cheers

Phill

[steven-g]

If you are confident using script and batch files how about trying VBS. The problem with scripts is they cannot make choices in a dialogue box within autocad, using +PUBLISH will let you enter a dsd file name but then still send you back to a dialogue box. However if you use VBS you can then imitate keyboard entry using the "sendkeys" command. Long story short, change the extension of the attached txt file to vbs and double click. It may not work on your system straight away, you will need to alter paths and file names. But hopefully it will give you a starting point for automating your tasks.

PS. all the sleep commands are just to slow the script down to allow you to see what is going on, but also to allow autocad time to operate each command.

[mrfilly]

Thanks Steven,

Look promising. Got it working on a 2010 machine, just need to figure out the LT machine.

Cheers

Phill

[pendean]

Tap this old link for some LT guidelines (which is not exposed by Autodesk to VB and may or may not actually violate your LT license agreement):

http://forums.augi.com/archive/index.php/t-57513.html

[steven-g]

I wasn't aware that this method might even be considered a violation, as it does nothing to change the way that autocad operates. Even if it falls within a grey area then my apologies to Autodesk. That said look here for a full description of the sendkeys possibilities. http://msdn.microsoft.com/en-us/library/8c6yea83.aspx

[pendean]

It may not be, but the licensing language is written in such a way that it's worth keeping in mind.

[steven-g]

It is a bit ambiguous, but looking further there are a number of references within Autocad documentation to using VBScripts to create installation deployments. So I don't think there could be questions when using VBS in other ways. If anyone from Autodesk is watching I stand to be corrected.