installation package

i created a mini-addressbook (like the ms-outlook's address book ) to practice/learn visual basic programming. i used ADO connection and an access file (.mdb). i used vb6. now when i try to crate a package.. an installer that is, it creates too big package for a mini-addressbook program. :(. what ive found it was it includes the whole DCOM (maybe) library(?) file in the package. now my question is is there a way i can make a smaller package w/o ommiting the required file for ADO connection? or maybe is there a redistrib file only for ADO? smaller lib.
LVL 3
iboAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VbmasterCommented:
One might wonder why you use databases at all. ;)
0
barnackyCommented:
If you are using ADO, I am pretty sure you need to install MDAC.  And if you need to install MDAC, you have to install DCOM.  Of course, you can create a distribution package without these components, if the end-user already has them installed.
0
barnackyCommented:
If you are using ADO, I am pretty sure you need to install MDAC.  And if you need to install MDAC, you have to install DCOM.  Of course, you can create a distribution package without these components if the end-user already has them installed.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

leg1Commented:
I would guess it's a common problem.  I thought I had read that if you choose to install the program from the web that you could choose to have the bootstrap and support files downloaded from MS.  If true, this would reduce the size of your file and if a person had the files on his disk they wouldn't be downloaded.  I haven't gotten too far with this.
If you really want to go ahead with this and are not committed to ADO you might want to switch to DAO.  More features and a smaller footprint.
0
leg1Commented:
I would guess it's a common problem.  I thought I had read that if you choose to install the program from the web that you could choose to have the bootstrap and support files downloaded from MS.  If true, this would reduce the size of your file and if a person had the files on his disk they wouldn't be downloaded.  I haven't gotten too far with this.
If you really want to go ahead with this and are not committed to ADO you might want to switch to DAO.  More features and a smaller footprint.
0
iboAuthor Commented:
i dunno.. well i could have used other thing/way like just using the 'data' control in vb but i want more control on my output (like using sql statements and pre-formatting data).

anyway i was only praticing/learning ado/v/sql etc for my future plan on an online database.

yeah its the mdac_typ.exe w/c is 8MB.
and my vb prob is approx 130K only. :/
0
Éric MoreauSenior .Net ConsultantCommented:
Your case isn't new. A lot of applications have more components to distribute than the size of the application itself!

Concerning DCOM, it is only necessary on Windows 9x since it is included in NT and in W2K.
0
dde13Commented:
using ado, there is really no way of excluding mdac.  my understanding is that you are thinking about web distribution.

you have four choices:
1) convert all ado controls to dao (prolly not entirely feasible, if youre using some of the cooler ado functions).

2) package your application in multiple .cab files.  this allows for the instability of a user's internet connection, but still makes the overall package quite large.

3) exclude mdac from your primary package and provide it as a second, optional package for the end user to implement if they see fit.  many computers built recently have mdac 2.0  or 2.1 (first appeared, nt-wise, around sp3 or 4, i think).  using vb6, you prolly used 2.0 for the ap.

4) if youre really ambitious, you can write your own installation, packaging the exact .dll files you need.  dont forget to check against the registry and update the registry with the added files.  this option is not for the faint at heart.

ado was really designed for larger applications.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
iboAuthor Commented:
thx ppl for u suggestions
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.