MFC DLL needs to be called from Non-MFC VB.
Couple of ways to do this. Use a regular dll instead of a MFC extension dll.
Export the method you want and then you can use it from VB as if it was a
Win32 dll. Alternatively, make a COM server(not recommended) and then you
can use any of the languages that understand COM.
--
Ajay Kalra [MVP - VC++]
Quote:
> I understand that a DLL using MFC needs to be called with a MFC interface,
> but that there can be an alternative method that uses a "bridge"
interface.
> Does anyone have any suggestions? My DLL will be doing a lot of string
> formatting from some string arrays I am passing to it. For the string
> arrays it was suggested to use the SAFEARRAY in a VARIANT* as in Q167668
but
> this is an Automation plus it's compiled as an out-of-process *.exe.
> I did see that Ben Ezzell has some kind of interface method or rather some
> kind of translation interface called ErrorShell.dll but I haven't been
able
> to find it.
> I'm open for all suggestions.
> regards,
> thomas
