Visual Basic creates ActiveX style DLL's rather than "pure" traditional DLLs.
I assume that EFS's DLL capability relates to a pure standard DLL, but just wondered whether anyone could clarify this for me.
TIA
There is a product called Visual DLL which will post-process a VB style DLL, but it's pricey and I have only a one-off need to create a standard DLL from a VB module.
I assume that EFS's DLL capability relates to a pure standard DLL, but just wondered whether anyone could clarify this for me.
TIA
There is a product called Visual DLL which will post-process a VB style DLL, but it's pricey and I have only a one-off need to create a standard DLL from a VB module.
Comment