Create the sub-programs as VB DLL projects.  Then when the user calls the 
program, you can check to see if the VB DLL is on the machine and then you 
can install the most current DLL onto the users machine.  This will keep the 
users current with most updated DLL file that they need.


>From: bmartens@k...
>Reply-To: "professional vb" <pro_vb@p...>
>To: "professional vb" <pro_vb@p...>
>Subject: [pro_vb] Program structure guidance
>Date: Mon, 21 May 2001 21:28:25
>
>I am beginning  to write an  application where there will be a  main menu
>in  a master program that will allow the user to choose from a variety of
>other programs to run.  My problem is that I only want to copy and install
>the components to the user's pc as they need them.  I would like them to
>click on the program they need and the main program will check to see if
>they have the latest version on their pc.  If they do it will run, if they
>don't the latest version of the program will be copied to their pc along
>with any dependent files, register the files if necessary, and then start
>the program.  My question: is there another way to check and see if the
>dll files are the latest version (other than by the date of the file),
>what directory or directories do dll's have to be copied to, and how do I
>register the dll through code?  My whole point in doing things this way is
>the user will only have to have the main program installed, and then they
>will only have the programs they need moved to their machine and they will
>always have the latest version.  I think I have a vague handle on how to
>accomplish this, but I would appreciate your feedback so I can get off to
>the right start.