I suppose if you bypassed the problem by creating your Win::OLE object in the child thread, you'd end up with the same problem later when you need to do something with it in the parent?
Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.
That's the idea I'm toying with now. The issue I'm going to run into with that implementation is that the Win::OLE object is actually "passed" to my code from the VB app via the RegCallback() routine. I assume that even if I have a child spawned at that point that the PerlCtrl internals will still use the parent thread for subsequent calls from the VB app.