Re: adding modules

You keep asking about this in the CB, which OS are you running?
The Makefile.PL states:

unless ($^O eq "MSWin32" || $^O eq "cygwin") {
    die "OS unsupported\n";
}
[download]

Which suggests you are not running cygwin or a win32 variant.

Update: Are you running a 64bit version of windows? If so $^O will be 'MSWin64'.
Update 2: Corion has informed us (in the CB) that you are running Fedora, so trying to install a module for Windows will not work. What are you trying achieve with Win32::OLE?.

Hope this helps

Martin

Comment on Re: adding modules Select or Download Code

Replies are listed 'Best First'.
Re^2: adding modules by ketaki (Acolyte) on Jul 03, 2008 at 11:02 UTC
the OS on my system is windows32, but i am installing this module on the web server. i am trying to link a excel worksheet with the perl/cgi script which i view on the browswer. my web server has cgi and perl on it. i dont have a perl compiler/interpreter on my computer.	[reply]
Re^3: adding modules by marto (Cardinal) on Jul 03, 2008 at 11:10 UTC
I don't know how many times people can tell you this, but Win32::OLE is not going to work on a linux/unix server. Why not use SpeadSheet::ParseExcel or something along those lines to achieve your goal? Also please read How do I post a question effectively? and the PerlMonks FAQ, IMHO you need to put in more effort to your posts, and start taking the advice people are giving you, otherwise you are wasting our time, and yours. Martin	[reply]
Re^3: adding modules by bigmacbear (Monk) on Aug 07, 2008 at 23:22 UTC
If you are simply using Excel to maintain tabular data that will eventually be processed by a CGI script, you can do yourself a big favor by exporting the data into a format that is easier for Perl to digest. Excel can export a worksheet in HTML format, which can then be read with any of the HTML parser modules or simply uploaded to the server for direct consumption by browsers; or it can export the data as a CSV (comma-separated variable) file, for which there are other modules with which Perl can massage the data. On the other hand, if you want to use CGI to massage data already present on the server to produce a file intended for consumption by Excel, your best bet is to name the script with a .csv extension, and produce valid CSV output from the script (preferably with a module designed for the purpose). Internet Explorer will (by default) then open the CGI script in Excel, embedded in your browser window. A naive approach to parsing CSV with split() or creating CSV with join() will often work if you are sure your data will never contain embedded commas or quotation marks. However, that is only a subset of valid CSV; hence the recommendation to use modules, which handle these cases better than split and join are capable of. HTML, on the other hand (and particularly Microsoft generated HTML) must be parsed rather than analyzed with split and join, and thus the modules are essential. Hope this helps.	[reply]