>Hi,
>
>I can't seem to find info on this topic in the help files (because it is always refering to the installation assistant). I'd like to know wich DLL(s) I need to install on the computers that will run my VB programs. I don't want to use the assistant because most of my apps are located on the server and the users do not each have a local version on their machines. I guess that my question could also be "Is there a way to compile the procedures or the entire DLLs used in my project into my final EXE?"

If you want to know what you have to distribute, you can use the assistant (Package & Deployment Wizard) and build a package. Once it will be done, you can open the setup.lst file. It will contain the list of files (mostly DLLs and OCXs) that you need to distribute.

Because VB doesn't support static linking, you can't have a EXE that contains everything needed by your application. The only way is to use a 3-party application like Fusion (see it http://www.bit-arts.com/products/fusion.shtml).