I would like to create a DLL using VB, but NOT CREATING a Class, which forces invokation of the routines/functions stored in the DLL to be called as methods of a "ficticious" class. Rather, I would like to create my functions as standard functions in standard modules, so when called they are called as if they were normal VB functions

Is it possible? And, if so, how?

thanks
gisvb

You can set your class to global multiuse. A class that is global multiuse does not require instantiation.

thanks, after tiding my code, the invokation of a function stored in a dll crashes because it can not find the "entry point"

I am using VBA as main language, and the dll has been built using VB Studio 6... I am using a simple function like

public function multiplicar(a as double, b as double) as double
 multiplicar=a*b
end function

Any suggestions for that ?

thanks

I assume you are working off a dll that has a globalmultiuse class. Try creating a new Dll with the same functions (cut and paste). It may be when switching over the dll went flaky.

thanks. I tried creating from scratch, but it can find the entry point.

It should be some basic error on my side, since all the stuff is very simple, but I must have missed something.

Anyway, the VBEditor recognizes de function, because when writing the name and the opening parenthesis it shows (in a tip) the arguments, so...... but at run time something happens.....

Any suggestions on that?

thanks again

Does anyone know how to "extract" the function names contained in a dll?. I have read that the exported names in a dll might have suffixes added to the function names,... so maybe I have to check now what function names/entry points my dll has....

You said a new dll can find the entry point. Is this a typo? If not, why not just go with the new dll?

sorry, yes, it was a typo.... Entry Point CANNOT be found, so I am stuck here, without knowing what more to test... maybe registering through regsvr32???

If you have not registered, then do so. Regardless of whether you are going to instantiate the DLL it still needs to be registered.

I registered the dll successfully, but running the program again, crashes as usual because it is unable to find the entry point

Has to be something basic that I am doing wrong, or my computer has a strange setup somewhere...???