Jenda Krynicky wrote: > > It's also quite often better to wrap the functionality in a DLL using > ActiveState's Perl Development Kit's PerlCtrl. VB is generaly more > happy working with COM/OLE objects than with external applications.
Another similar approach would be to create a scriplet that contains the perl code you want to make available. Just search for "Windows Script Components" and you should find enough information to get started. The only complaint I have about WSCs is that errors are not reported via COM exceptions, but rather as pop-up messages from the engine (and that only when the <?component error="true"?> PI is in your scriptlet). -Mike _______________________________________________ ActivePerl mailing list ActivePerl@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
