VB Forum / Win API / September 2007

The path can be either a fully qualified path, a relative path to the
current directory, or any folder in the Environment %Path% statement.

The most likely problem is because the search path is different for your
Compiled App and the App when run in the IDE.

Just for grins write a quick app with one form and one textbox that outputs
the App.Path. Then run it in the IDE, then compile (make) the app and run
the exe. Note the difference.

-ralph

CuriousP <CuriousP@discussions.microsoft.com> schrieb im Beitrag
<B8BF0824-DA61-423D-A917-B8E7D31CA371@microsoft.com>...

The search path for a DLL given in a declare statement without any file
path is:
- The directory from which the app has been loaded
- The current directory of the app
- The Windows system directory (e.g. Win 9x: C:\WINDOWS\SYSTEM; Win NT:
C:\WINDOWS\SYSTEM32)
- Win NT only: the 16 bit Windows system directory, e.g. C:\WINDOWS\SYSTEM
- The Windows directory, e.g. C:\WINDOWS
- The directories listed in the PATH environmental variable

So, just put the DLL's filename without any file path components between
the quotation marks behind 'Lib'.

The path can't be specified at run time but only at design time, because
the declare statement isn't a real code statement which is executed at
design time; instead it is a compiler directive resolved only once when the
code gets compiled.

I believe that the string has to be specified at compile time.
App.path cannot be resolved until run time;