Well here's a creative hack - you could install a second 64-bit perl and have it wrap COM objects with a quick and dirty REST web service, then replace the COM calls in the 32-bit perl with web requests to the web service!
Of course if the whole program is all about COM calls, that isn't very practical, but if you only need COM for a few edge features, like exporting to MS Word, this could be faster than fully debugging the app on a new perl environment with new module versions.
Am I guessing correctly that you don't have a copy of the perl environment that this app runs in? Because otherwise you could locally build a whole new 64-bit windows perl environment with all the same module versions, and bring that to them on a thumb drive to quickly replace the existing perl environment in a short visit.
If you don't have a copy of that perl environment, you should probably ask if you can make one. It's in the customer's best interest if the versions are known and recorded somewhere.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.