WString 64 vs 32 bit DLL

Targets Windows
1

I need to use a 32 bit DLL and have a call that takes a wstring.
It works fine on a 32 bit compile of my app, but fails when compiling 64 bit.
Every other function works just fine.

Does this make any sense?
Suggestions to work around?

2

I should be more specific. I get a function not found error.

3

makes perfect sense
64 bit apps cant call & load 32 bit DLL’s
You’d need to have a helper 32 bit app you start that loads the dll that you can then talk to

4

Norman,

I had no idea. I was sure I could still call a 32 bit dll from 64 bit windows (just not the other way around). Well this just sucks.

5

https://docs.microsoft.com/en-us/windows/win32/winprog64/process-interoperability

They mention some other ways you might be able to use it with an out of process COM server etc - basically like a helper

6

http://documentation.xojo.com/api/networking/ipcsocket.html

You can create a simple protocol and Talk IPC with your helper (listener) for simple things like requesting and obtaining a string.

This is simple and fast.

I like this approach, and more because I prefer solutions portable for other platforms.