Phil !
you wrote :
===
I want to run perl code as a function/module inside EXCEL, in the same way that
one can run VBA.
===
yr wish as stated above seem to me rather
strange /not to say more/
For my part I never had such a wish - working
with both perl & VBA.
Am I missing some point here ?
Can yu
Steven,
That's sortof what I expected, but figured if I could do it with Perl that's
what I would prefer.
Thanks,
Phil
---
Suresh,
I did not just "[go] clickty-click with the mouse", but I confess I did not
analyze the url
What do you want this macro to do?
You can create an instance of the COM object that Exposes Excel to VB
(and any other language that understands COM -- like perl)..
---
use Win32::OLE;
$excel= Win32::OLE->new("Excel.Application");
But that's not code running like an Excel macro...
If one examines the url provided (rather
than just going clickty-click with the mouse),
one can see how to get to their sites (see PS below).
However, those sites won't answer your need, viz:
"[you] want to run perl code as a function/module
inside EXCEL, in the same way that
The URL you provided does not work.
I was able to find some stuff under "jcmcnamara" in the URL where perl is
being used to create an excel file. This is not what I want to do. I want to
run perl code as a function/module inside EXCEL, in the same way that one
can run VBA.
Thanks,
Phil
Da
Rod Butcher wrote:
>>my $PE32 = pack 'LZ', 296, 0, 0, 0, 0, 0, 0, 0, 0, ' ' x 259 . "\0";
>>
>># BOOL WINAPI Process32First(HANDLE hSnapshot, LPPROCESSENTRY32 lppe);
>>
>>Win32::API->Import('kernel32', 'Process32First', 'IP', 'I') or
>> die "import CreateToolhelp32Snapshot: $!($^E)";
>>
>
$Bill Luebkert wrote:
Rod Butcher wrote:
It looks like MAX_PATH defines the length of variable length string
szExeFile, in C. Hence for C this is a legal field definition.. but it
looks to me as if Win32::Api::Struct is not handling it as such. Neither
my Perl nor my C is strong enough to fi
Rod Butcher wrote:
> It looks like MAX_PATH defines the length of variable length string
> szExeFile, in C. Hence for C this is a legal field definition.. but it
> looks to me as if Win32::Api::Struct is not handling it as such. Neither
> my Perl nor my C is strong enough to figure out a way ar
