Well, it would still work the same way...just that a few things are specific to the compiler/linker you are using. I am not trying to be smart here, I want to help.
I assume that Turbo C++ has a generic dll project type. Start with that. (The switches should be right.)
The method used in the tutorial is to pass DBPro the C++ mangled function prototype. That is what the string resource is, more or less. If you used the values from the tutorial, it probably failed because name-mangling is compiler specific. The name mangled function name comes from the dll itself. Take a binary editor (not NOTEPAD) and you can get the mangled name from either the .lib, or the .exp It is also in the MAP file in MSVC++, and the .obj file, too. So, make sure that the name is the same in your string resource.
jzDBP.dll??0CjzDBP@@QAE@XZ??4CjzDBP@@QAEAAV0@ABV0@@Z?
fnjzDBP@@YAHXZ?jzGetValue@@YAHXZ?jzMSGBox@@YAXPAD@Z?
jzS32DivByPow2@@YAHHH@Z
Above is from jzDBP.exp, which is the exports file. You also have to have the prototype formatted so that DBPro recognizes the function.
Well, all that is only if the dll compiled correctly, and you put it in the correct place...which i assume that you did, so...I think that name-mangling is your culprit, not TurboC++, or DBPro.
