🚀 go-pugleaf

In article <1992Sep13.065343.25286@silogic.uucp> markd@silogic.uucp (Mark C. DiVecchio (K3FWT)) writes:
>
>I am using Borland C++ and OWL. I wrote a simple program that puts
>up a dialog box when exiting. It runs fine when run from the Borland
>C++ environment.
>
>When I run it by double clicking on the program name using the
>File Manager, it won't put up the dialog box on exiting but rather
>gets a Error 5.
>

You're right in thinking that your application needs to access
BWCC.DLL.  Since the compiler uses the custom control DLL, it loads it
when you enter the development environment and running your
application within it is no problem.  To ensure that BWCC.DLL is
loaded by your application, read the on-line documentation within the
OWL directory.  I, too, was surprised that there was no mention of
this within the printed documentation.

Basically, you are looking for references on forcing the loading of
the BWCC.DLL, by making a simple call to one of its functions, and the
need to link in the BWCC library when you compile your application.
The references are in two places within the documentation.  For speed,
just GREP "BWCC" the doc files.
-- 
yev_g@athena.mit.edu
500 Memorial Drive, Cambridge, MA.  [ Yevgeny Gurevich ]