
OCX's Outside the Win\Sys Dir ? Beginner Question ...
writes:
Quote:
>'m fairly new to Visual Basic programming, but I have run into a
>problem trying to create a 'clean' program. I have a need to create a
>program that keeps all DLLs and OCXs and any other file called within
>the application's directory with NOTHING installed to the
>Windows\system directory.
> Any hints ... Where does Visual Basic 4 keep track of where to call
>the libs from ? Is it easily manipulated ?
> Also on a similar note, how do I set the working environment in the
>Visual Basic IDE to a directory other than VB ?
Win searches the Current Dir first, then Windows, then WinSys, then the
Path specified, in some cases it seems to search a Netpath too.
This is NOT configurable. THe probem you WILL have is that you have ver
1.1 of an OCX in your app dir. Win will not use it, if ver .9(b) is
already loaded into memory.
You can read your INI file for a work dir and ChDir to it in code, or set
the working dir in the properties dialog of ProgMan/Start menu
HTH
-Mike