Re: Problems with Microsft's new Office 'XML'

You are referencing the "xls" file which is still binary. Change your filename to "spreadsheet.xml" and save the file as xml.

Using your first script with an "xls" file causes the error you see, however when I use it on the same file saved as "xml" it does not report an error.

Update

Here is some code to dump the xml file.

use strict;
use warnings;
use XML::Simple qw(:strict);
use Data::Dumper;  

my $config = XMLin('./Book1.xml',forcearray => 1,keyattr => ['']);
print Dumper($config);
[download]

Comment on Re: Problems with Microsft's new Office 'XML' Download Code

Replies are listed 'Best First'.
Re^2: Problems with Microsft's new Office 'XML' by graq (Curate) on Oct 05, 2005 at 07:39 UTC
You are referencing the "xls" file which is still binary. Change your filename to "spreadsheet.xml" and save the file as xml. OK. This is meant to be an automated process, removing the human interaction - how do I do this with Perl? <a href="http://www.graq.co.uk">Graq</a>	[reply]
Re^3: Problems with Microsft's new Office 'XML' by Corion (Patriarch) on Oct 05, 2005 at 07:47 UTC
As always, you do this by using Win32::OLE to automate Excel. The steps are the usual six steps: Start the Excel Macro Recorder Perform the desired action(s) manually, in your case, save the file as XML Stop the Excel Macro Recorder Inspect the generated VB code Check that the generated VB code does what you want Translate the generated VB code to Perl / Win32::OLE invocations There are many examples on this website which should give you a good start on how to do the translation. It consists mostly of `s!\.!->!` applied to every line of the code, and you will have to exchange the global properties like "ActiveWorkSheet" by the local values you get from `$excel->OpenFile()`.	[reply] [d/l] [select]