PureBasic Forums - English

Restored from previous forum. Originally posted by dmoc.

Not sure yet if this actually IS a bug but it sure is acting strange. For the past week I have been using OpenLibrary() inside a procedure inside a file I "include" in my main file. All has been fine until today, the library being opened has not changed at all (3rd party) and is still in exactly the same directory. The procedure containing the Openlibrary() has also not changed but now it fails to open the library everytime. I have relocated the main exe to the same directory as the DLL but still Openlibrary() fails. Any clues anyone?

Restored from previous forum. Originally posted by Danilo.

On F5-compile the DLL must be in the
compiler path PureBasic\Compiler\

cya,
...Danilo
(registered PureBasic user)

Restored from previous forum. Originally posted by dmoc.

I'm not compiling a dll but I am moving the compiled exe into the same directory that the dll I'm trying to open lives in.

Restored from previous forum. Originally posted by dmoc.

Update: I took the OpenLibrary() call out of the procedure and into the main code and it works ok. @Fred: Are there any known bugs about this? If not then I'll spend some time and try and isolate the situations in which it fails. If there are known bugs then please let me know and save me some much needed time!

Restored from previous forum. Originally posted by fred.

No bug seems reported about this fact. I use OpenLibrary() on regular basis and all is ok.. Very strange.

Fred - AlphaSND

Restored from previous forum. Originally posted by dmoc.

I'll check some more as soon as I have time.