You can also switch to the combination of Text::CSV_XS + Excel::Writer::XLSX. The Text::CSV_XS release comes with csv2xlsx script (documentation).

You should still be able to use Win32 OLE together with a 64bit Office. Maybe switchting to a 64bit Perl like Strawberry Perl helps?

Below is the error I got. I'm on Strawberry Perl x64 bit. Turns out I need to remove use Win32::OLE::Const 'Microsoft Excel';.

use strict;
use warnings;
use Win32::OLE;
use Win32::OLE qw(in with);
use Win32::OLE::Const 'Microsoft Excel';

my $EXCEL = Win32::OLE->new("Excel.Application","Quit");
    $EXCEL->{"Visible"} = 1;
    $EXCEL->{DisplayAlerts}= 0;
    $EXCEL -> {"SheetsInNewWorkBook"} = 4;
    
my $Workbook = $EXCEL -> Workbooks -> Add();
[download]

This is perl 5, version 32, subversion 1 (v5.32.1) built for MSWin32-x64-multi-thread Microsoft® Excel® for Microsoft 365 MSO (Version 2208 Build 16.0.15601.20526) 64-bit No type library matching "Microsoft Excel" found at test_4.pl line 5. Win32::OLE(0.1712): GetOleTypeLibObject() Not a Win32::OLE::TypeLib object at C:/Strawberry/perl/vendor/lib/Win32/OLE/Const.pm line 49.

I use Spreadsheet::WriteExcel to write Excel spreadsheets occasionally. This is on 64-bit Office365 and Strawberry Perl.
Spreadsheet::Read is used daily here without any issues.

Neither require me to use OLE modules.

By the way, it converts one CSV file to one XLSX Excel file, but converting multiple CSV files into one Excel file should be relatively easy with only some slight tweaking.

"What's unique about this Perl script is that it does not rely on any Perl modules ..."

The first three lines of code:

use 5.004;
use strict;
use warnings;
[download]

BUT

$ corelist warnings

Data for 2022-05-27
warnings was first released with perl v5.6.0
[download]

So, clearly this will not work with Perl 5.004. If you're going to assert a minimum version, ensure you have tested with that version.

On an unrelated note, please stop messing with colours. I'm pretty sure that you've been pointed to "Writeup Formatting Tips" in the past; if not, or if you didn't read it, please do read it, paying particular attention to the Don't get carried away section (near the end). What it says there about <font> tags applies equally to bgcolor attributes. Putting your <code> content inside a <table> with BGCOLOR=66CCDD is not a clever way to exploit what perhaps you considered a loophole.

If you want to see fancy colours when viewing code, go to your Display Settings and set up appropriate CSS. Don't force your preferences on others.

— Ken

Okay, I removed the colors.

Yes, I know. To make it work, I added a dummy file into the lib directory of perl called warnings.pm and it has a number 1 in it. So, that way I can leave the warnings in it yet will work on old Perl! Yes, maybe I should clarify that. Right? But I figured that the number of people who would need that advice is really small. I could probably count on one hand how many will run this code using an old perl interpreter. And of course, when they try it, it's going to say that there is no such thing us warnings.pm. Now, at this point, I hope these guys will use their brilliant mind to either remove the first line where warnings is mentioned or they'll add a fake warnings.pm file like I have.

You've done a really bad job at trying to deliver one thing, badly reinventing wheels. Why would a non-masochist use anything like this?

I don't know. The goal is to get an XLSX file. Is it not? This thing does the job right. In the next version, I may add an LZW compressor written in pure Perl to deliver smaller content. :-)