With preemptive strike i.e. use of Win32::LongPath and switching of the default to ensure proper Unicode handling if paths use characters outside your ANSI codepage:

use Win32::LongPath 'getcwdL';
use File::Spec::Functions 'catfile';

use Win32::OLE;
Win32::OLE-> Option( CP => Win32::OLE::CP_UTF8 );
# ...

$pathfile3 = catfile( getcwdL, 'Template', "$input.xlsx");
$Book2-> SaveAs( $pathfile3 );

[download]

Edit. It occurred to me, you may want to run the script while in another directory:

use FindBin;
use File::Spec::Functions 'catfile';

use Win32::OLE;
Win32::OLE-> Option( CP => Win32::OLE::CP_UTF8 );
# ...

$pathfile3 = catfile( $FindBin::Bin, 'Template', "$input.xlsx");
$Book2-> SaveAs( $pathfile3 );

[download]

There is a regression above, in that I don't assume you plan to work with non-ascii file paths (while, still, it's OK to pass Unicode strings to Excel - which I think is not uncommon even for ascii-people). The reason is there seem to be ugly details not covered by Win32::LongPath or other modules I know -- both $0 and $FindBin::Bin contain encoded (ANSI-CP) strings, so there is a mess not only with decoding, but testing what happens if path to perl script has non-ANSI-CP characters in relative path.

In reply to Re: Win32::OLE SaveAs Problem by vr
in thread Win32::OLE SaveAs Problem by Sasuke300

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.