Win32::OLE but it's a bad idea. You will also need some strongish VBscript-ing skills to go with it since Many Win32::OLE options are not documented and knowing the VBscript equivalent will allow you to find functions that you need. The actual process is to open the Microsoft Excel application, read the file into Excel with your script (Don't manually try and interact with Excel when the script has it open), make your changes, save the file, and then close Excel again.
From a data-safe standpoint there is very little keeping you from overwriting something accidentally using this process. Additionally these scripts are not very portable since they rely heavily on the Excel settings embedded in each computers Excel installation.
The alternative is to export your perl data with a .csv file using the excellent Text::CSV and either import the data to the existing Excel manually (Data/From Text/FileName.csv) or do the same with a Macro or PowerShell.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
