By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,313 Members | 2,798 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,313 IT Pros & Developers. It's quick & easy.

What Access Runtime files are needed to deploy? (2002/XP)

P: n/a
Hello,

I have an application that I have been deploying with the Office 2002 / XP
Developers Edition Package and Deployment wizard. The package that it
creates is 180 MB in size. I would like to use a third party packaging /
setup script instead to reduce the size of the package. I spoke with
someone in passing once that said he was able to reduce his package to about
a third of it's size by using another program to package it, but I didn't
ask which files were required.

I do own the Developers Edition, so I am licensed to distribute this, I
just need to know which files I need to include to be able to deploy the
program properly.

Even a link to another site (which I wasn't able to find on Google, but
maybe it's my method of creating search strings), would help a bunch.

Thanks!
I
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi,

See SageKey sofware http://www.sagekey.com/ , this is the best packager for
Access XP

Regards
"Jozef" <me@you.com> a écrit dans le message de news:
qQhXe.219787$Hk.214335@pd7tw1no...
Hello,

I have an application that I have been deploying with the Office 2002 / XP
Developers Edition Package and Deployment wizard. The package that it
creates is 180 MB in size. I would like to use a third party packaging /
setup script instead to reduce the size of the package. I spoke with
someone in passing once that said he was able to reduce his package to
about a third of it's size by using another program to package it, but I
didn't ask which files were required.

I do own the Developers Edition, so I am licensed to distribute this, I
just need to know which files I need to include to be able to deploy the
program properly.

Even a link to another site (which I wasn't able to find on Google, but
maybe it's my method of creating search strings), would help a bunch.

Thanks!
I

Nov 13 '05 #2

P: n/a
Not looking for a packager. Although I agree that Sagekey is the best (I
live very close to them) I'm just looking for the list of files that Access
needs to run. I was hoping that I could find out without a whole lot of
trial and error.
"Indrid Colt" <in****@colt.com> wrote in message
news:Op********************@weber.videotron.net...
Hi,

See SageKey sofware http://www.sagekey.com/ , this is the best packager
for Access XP

Regards
"Jozef" <me@you.com> a écrit dans le message de news:
qQhXe.219787$Hk.214335@pd7tw1no...
Hello,

I have an application that I have been deploying with the Office 2002 /
XP Developers Edition Package and Deployment wizard. The package that it
creates is 180 MB in size. I would like to use a third party packaging /
setup script instead to reduce the size of the package. I spoke with
someone in passing once that said he was able to reduce his package to
about a third of it's size by using another program to package it, but I
didn't ask which files were required.

I do own the Developers Edition, so I am licensed to distribute this, I
just need to know which files I need to include to be able to deploy the
program properly.

Even a link to another site (which I wasn't able to find on Google, but
maybe it's my method of creating search strings), would help a bunch.

Thanks!
I


Nov 13 '05 #3

P: n/a
Trying to figure out what files you need, and building your own install is
indeed a big job.

I believe that in excess 1000 registry entries are made during a install.

I did not realize that the 2002 install were so large. I used the a97, and
installs came about to 15 megs in size.

I now use a2003, and we got a little more then double the size (about 32-35
megs in size). I have supplied a good number of runtime installs over the
web, and with high speed, the downloads are a couple of minutes at most
(done it on the phone while the client waits).

I know that a2000 was about 150 megs in size due to it including IE.

However, was not aware that a2002 produces such large installs.

For the time and troubles involved, I would either go with sagekey, or
consider upgrading to a2003.

Once I ensure that the client has got ms-access installed, then updates to
applications are zipped mde files..and they are super small.........

I can't remember the a2002 producing such large files, but a2003 certainly
does not...

The only downfalls of the a2003 installer is that is now does not support,
or package activeX controls for you. (however, as a nice touch, the 6
standard controls such as the calendar, listview, treeview etc are INCLUDED
BY default). In effect, this means you never have to worry about the activeX
controls during a install (assuming you stick to the controls that are
supported by access). The other downfall is that a2003 requites windows
2000, or xp. So, office 2002 is the LAST version to support both windows
98SE, or windows xp.

I also like the a2003 packager, as it makes the desktop shortcuts for you.
So, the package wizard has been MUCH simplified.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #4

P: n/a
Thanks for the info Albert!

I was asking about the 2003 package a while back, but no one was able to
help at the time, so the information you've provided is appreciated.

I've tried excluding the system files before to get it down to about fifty
meg, but that seems to be bad news as well, and never seems to work on half
the installs.

I will definitely do the upgrade to 2003 if it creates a smaller package.

Thanks again!


"Albert D. Kallal" <ka****@msn.com> wrote in message
news:wRQXe.528050$s54.290401@pd7tw2no...
Trying to figure out what files you need, and building your own install is
indeed a big job.

I believe that in excess 1000 registry entries are made during a install.

I did not realize that the 2002 install were so large. I used the a97, and
installs came about to 15 megs in size.

I now use a2003, and we got a little more then double the size (about
32-35 megs in size). I have supplied a good number of runtime installs
over the web, and with high speed, the downloads are a couple of minutes
at most (done it on the phone while the client waits).

I know that a2000 was about 150 megs in size due to it including IE.

However, was not aware that a2002 produces such large installs.

For the time and troubles involved, I would either go with sagekey, or
consider upgrading to a2003.

Once I ensure that the client has got ms-access installed, then updates to
applications are zipped mde files..and they are super small.........

I can't remember the a2002 producing such large files, but a2003 certainly
does not...

The only downfalls of the a2003 installer is that is now does not support,
or package activeX controls for you. (however, as a nice touch, the 6
standard controls such as the calendar, listview, treeview etc are
INCLUDED BY default). In effect, this means you never have to worry about
the activeX controls during a install (assuming you stick to the controls
that are supported by access). The other downfall is that a2003 requites
windows 2000, or xp. So, office 2002 is the LAST version to support both
windows 98SE, or windows xp.

I also like the a2003 packager, as it makes the desktop shortcuts for you.
So, the package wizard has been MUCH simplified.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.