This is not a _process_ memory problem if he is creating a thread. The .dll will be loaded into the same memory map as the calling application (that's what does on in the LoadModule() function in Windows). Threads can share memory within the same process. I do this kind of thing, between different programming languages all the time. Just never between Blitz and PB.
I don't have PB but my best guess is the chap who pointed out that PB releases loads of resources when the DLL call returns. Make sure you are not dependant on anything that might live on the stack or only for the duration of the function call. If you can't get it to work that way... Hell grab a C++ compiler and build it in a language you can control :-)
Bug
I don't have PB but my best guess is the chap who pointed out that PB releases loads of resources when the DLL call returns. Make sure you are not dependant on anything that might live on the stack or only for the duration of the function call. If you can't get it to work that way... Hell grab a C++ compiler and build it in a language you can control :-)
Bug