Scheduling the printing of an Excel file which has an add-in from the command line using visual basic scripting (vbs) via wscript

25 August 2009

On a recent project, I was required to print out an Excel-based report which made extensive use of OSIsoft PI DataLink’s Excel Add-in on a scheduled basis (7 am daily).

Unfortunately, Excel does not easily allow for the printing of an Excel file via the command line via switches or parameters when calling Excel.exe (e.g. C:\Windows\MS Office\Excel.exe -print “C:\Reports\My Report.xls”).

I was able to find examples on the Internet which made use of cscript or wscript where one calls VBS code, and where one provides the file name as an argument, for example:

wscript “C:\Data\My Scripts\printXLS.vbs” “C:\Data\My Reports\Daily Analyser Excursion Report.xls”

Note the convention of using “” around full path filenames as they contain spaces.

The file printXLS.vbs would contain something akin to the following code:

Dim XLApp
Dim XLWkbk
Dim ObjArgs

set ObjArgs = wscript.arguments
if ObjArgs.count <> 1 then
wscript.echo “Invalid passed arguments”
wscript.quit
end if

Set XLApp = CreateObject(“Excel.Application”)
XLApp.Visible = False

Set XLWkbk = XLApp.Workbooks.Open(objargs(0))
XLWkbk.PrintOut
XLWkbk.Close False

XLApp.Quit

Set XLWkbk = Nothing
Set XLApp = Nothing
Set ObjArgs = nothing

The problem I experienced was Excel Add-ins are not automatically loaded in Excel applications created via Automation. This resulted in the Excel file printing but with OSIsoft PI DataLink Excel Add-in functions not being recognised and #NAME! appearing in the relevant cells on my printout.

The solution I found was to explicitly load the Excel Add-in via XLApp.RegisterXLL (“fullpath filename“)

So my VBS file looked like something this:

Dim XLApp
Dim XLWkbk

Set XLApp= CreateObject(“excel.application”)

XLApp.Visible = FalseSet XLWkbk = XLApp.Workbooks.Open(“C:\OSIsoft\Reports\Scheduled\PI Report – Analyzers – Quality Excursions.xls”)
XLApp.RegisterXLL (“C:\Program Files\PIPC\Excel\pipc32.xll”)

XLWkbk.Worksheets(“Report”).Calculate
XLWkbk.PrintOut
XLWkbk.Close False

XLApp.Quit

Set XLWkbk = Nothing
Set XLApp = Nothing

I also wanted to be able to specify the number of copies to print and which printer should be used namely PRC2 in my case. If the printer is not specified then the Windows default printer is used.

I also decided to allow one to specify the Excel workbook and which specific worksheet in the Excel workbook to be printed.

So allowing for parameters the VBS look something like this:

‘Arguments’1 Excel Name e.g. “C:\OSIsoft\Reports\Scheduled\PI Report – Analyzers – Quality Excursions.xls”‘
2 Worksheet Name e.g. “Report”‘
3 Printer Name e.g. “PRC2″‘
4 No of copies e.g. 1

Dim XLApp
Dim XLWkbk
Dim ObjArgs
Dim strFileName
Dim strWorkSheetName
Dim strPrinter
Dim intCopies

Set ObjArgs = wscript.arguments
If objArgs.count <> 4 Then
wscript.echo “Invalid Passed Arguments”
wscript.quit
End If

strFileName = objargs(0)
strWorkSheetName = objargs(1)
strPrinter = objargs(2)
intCopies = objargs(3)

Set XLApp= CreateObject(“Excel.Application”)
XLApp.Visible = False
Set XLWkbk = XLApp.Workbooks.Open(strFileName)
XLApp.RegisterXLL (“C:\Program Files\PIPC\Excel\pipc32.xll”)
XLWkbk.Worksheets(strWorkSheetName).Calculate
XLWkbk.PrintOut , , intCopies, , strPrinter
XLWkbk.Close False
XLApp.Quit

Set XLWkbk = Nothing
Set XLApp = Nothing
Set ObjArgs = Nothing

I was then able to use Windows Task Scheduler to call the VBS file to print my Excel files daily.

<a href="https://www.blog.idx.co.za/author/bruce/" target="_self">Bruce Bean</a>

Bruce Bean

New Business Development Manager

Bruce has over thirty years of experience in the consulting, information technology, project management and software development industries. His hobbies include karate, pilates, rebounding, piano and playing pool.

Show your love!

Recent Posts

HMS Networks Price Increase Effective January 2026

We would like to inform our valued clients of an upcoming price adjustment from our supplier, HMS Networks, effective 1 January 2026. This change reflects global market shifts that have impacted the industrial sector in recent years. Despite extensive efforts to...

EtherCAT Network Troubleshooting Success Story

IDX recently supported a client with targeted troubleshooting and networking assistance on a large EtherCAT installation within a new distribution sorting facility. The facility’s conveyor input and output (I/O) system was intermittently losing communication with the...

Unlocking Industrial Efficiency with the IDX Nexus Framework

In today’s industrial landscape, data drives decisions. Plants generate vast amounts of operational data daily, yet without the right tools, this data often remains siloed, inaccessible, or underutilised. Our flagship product, the IDX Nexus Framework, is designed to...

IDX and Lineview Drive Performance at Coca-Cola Peninsula Beverages

IDX has partnered with Lineview to implement a digital platform at Coca-Cola Peninsula Beverages (Pty) Ltd, aimed at enhancing front-line engagement in monitoring and improving line performance. As always, the real impact happens when people actively engage, and this...

IDX Attends the 36th Annual PI Meeting in Edinburgh, Scotland

Industrial Data Xchange (IDX) is proud to have represented Southern Africa at the 36th Annual PROFIBUS and PROFINET International (PI) Meeting, held in Edinburgh, Scotland, from May 12 to 16, 2025. This five-day event brought together key stakeholders from across the...

Sign up for our newsletter

Get exclusive updates and a sneak peek into our world every two months. Stay connected, stay informed.

Related Posts

We understand the importance of minimising downtime and maximising productivity in your plant. Through our innovative solutions, we work alongside you to streamline processes, enhance efficiency, and reduce costly downtime.

CONTACT US

Main: +27 (11) 548 9960
Sales: +27 (11) 548 9970

JOIN OUR COMMUNITY

Copyright @2025 Industrial Data Xchange. All rights reserved.