Did you build your copy of perl with Borland? If not, then you probably on a hiding to nothing.

Whilst DLLs ought to be independant of the compilers that produce them, my experience is that the DLLs produced when building perl extensions seem to have some peculiar dependancies that often make it impossible to use one built with Borland in conjuction with a perl built with VC++ (ie. AS).

I've not really tied down quite why this is the case, I did spend some time trying to investigate it, but got kind of demoralised and gave up. I have built some modules with Borland that result in a dll that work fine with AS, but mostly not.