Re^2: Exporting VBA code from Excel: Win32::OLE exceptions & orphaned processes

Thank you, thank you, thank you Anonymous!

Issue 1 resolved, for Excel 2007 on Win7:

File
-> Options
-> Trust Center
-> Trust Center Settings
-> Macro Settings
-> (x) Trust access to the VBA project object model

I'm sure it's something similar for XP.

For Issue 2, eval() huh? Interesting.

The $excel should be

$xl_obj = Win32::OLE->new('Excel.Application');

and most everthing else is the DoStuff to be eval'd.

I'll play around with that.

I still have the brute-force before/after process list trick to fall back on.

Mucho thanks.

Comment on Re^2: Exporting VBA code from Excel: Win32::OLE exceptions & orphaned processes