@^:
Yes, but if there is not only one dependency but maybe 2 or 3 with only one missing function this will be pita. DependencyWalker is a nice and clear solution that only takes seconds to find out where the problem is

whoa masterq32 I just realised I used kartoffel's nick to refer to you in my previous reply , waaay sorry I fixed it lol

you can load a library as often as you want, you just need to unload it by the same amount of calls. It's reference counted.

If the dll was loaded before, LoadLibrary does not load anything, it just returns the already existing handle and increases ReferenceCounting by 1.

Same goes for FreeLibrary. It first Decrements the referencecount by 1, and if it reaches 0, it unloads the library. So if you "load" a library 3 times, you have to "Unload" it 3 times. Otherwhise it's keept until your process exits.

^this thanks
was actually too lazy to type that since its stated on msdn

^ & ^

you misunderstood the point , if the engine couldn't load the dll after gamestudio was freshly reinstalled (it used to be able to load it at startup) ,then loadlibrary would also not be able to load the library because obviously there's an issue with the library and not gamestudio , thats what we meant .

@Rakscha: I know how LoadLibrary works, pretty good actually
The point is, what Wjbender said above.

The normal reason why Windows does not load a DLL is an unresolved dependency. Your DLL needs some other DLL that is not provided on your system. Maybe a certain DirectX version or something like that.

There is a free tool named "Dependency Walker" that you can use for fixing those problems.

Then i mssunderstood you. Because, if a library loaded before LoadLibrary will work! but you stated the opposite^^