I'm creating my first VB program.  The database table is in a .mdb format.
Is there any way to wrap the tables into the executable so that only one
file (the .exe) will be all another person needs.    Also, this small
program I am trying as my first project needed to occupy 5 MB of space when
the "SetUp Wizard" put the program together.  What is the best way of
telling WHICH of all the files that are supposed to go along with the
executable really need to go with it.  (i.e. to another computer using WIN
95)  Thanks.

Second, make sure you remove (uncheck) anything you're not
actually using from the References dialog and remove any custom
controls you're not using from the toolbox. If something is
included in either of these it gets included with the
distributables by the setup wizard whether you use it or not. If
you're in the habit of leaving a couple of dozen custom controls
sitting in the toolbox at all times, you're probably distributing
a couple of megs of files that the end user won't need.

One thing that I found helpful was to modify the "default"
project for VB (something like autoload.vbp in the VB install
directory). I removed everything from this project file that
wasn't required for VB to function. That way I only add the
controls and references that I actually need.

Joe

Never underestimate the power of a WAG.

http://www.citilink.com/~jgarrick/vbasic/

Besides Joe's good suggestions on removing references, there _is_ a way to
"incorporate the database into the executable" (other than a
self-extracting .EXE).  

The way to do it is to create the database on the fly by creating the
database
(MyWorkspace.CreateDatabase etc...) and then creating all of the tables and
fields, etc.
Not recommended.  Your maintenance costs go way up.  Just include the .MDB
with your app,
think of it like your new file template, just like MS Word uses .DOT files
or Excel uses .XLT.

- Brian Hutchison
  (The return address is spoofed so as to avoid spam.  )