Easy Public Declare ... question

[laudy]

When I am declaring a function from a DLL in a module, is it possible to variabilize the DLL that the function resides in (to allow for the DLL being located in different possible places)

Such as:
Public Declare API_Call Lib varDllPath (ByVal etc.....)

When I declare a Constant varDllPath and try to use that in the Public Declare statement... I get an error... "expected string constant".

Is there a way to variabilize the path to the DLL referenced in the declaration to allow for setting that at run-time?

Thanks, Dale.

[DerFarm]

ummmmm....isn't that the purpose of registering the DLL?

My understanding is that when a DLL is registered, the operating
system will find the silly thing no matter where the end-user
stupidly put it. The path to the contents of the DLL is in the
registry.

If this is the case, then all you have to do is guarantee that the
DLL has been registered. Presumably, you could check the
register for the name of the DLL before comencing processing,
and then put up a msgbox if you can't find it. I don't know how
to do that, and it would probably be more trouble than it's worth.

HTH

[JoshT]

Is there a way to variabilize the path to the DLL referenced in the declaration to allow for setting that at run-time?

I believe you can use the API LoadLibrary and related APIs to load a DLL and call its functions, but I've never used it myself.
http://msdn.microsoft.com/library/de...c/dll_0qr7.asp