|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I developer an ADP with Access 2003 and distributed it with a package created
wih Package Wizard from VSTO 2005.
When I tried to install the package onto my customer computer I noticed that
the installed Access 2003 runtime didn't include Service Pack 2003 for Office
2003.
I searched a lot and asked in an italian newsgroup and finally Giorgio Rancati
told me to visi this page: http://support.microsoft.com/kb/916176/en-us
I red that SP2 files are not included in the package and that I have to run
a chained installation. This means I have to deploy a package increased by
100 MB for each one of my applications.
Do you know any other solutions?
--
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution
|
|
I wrote and published (that is, here, search for "Sover" 21/7/06), how to
incorporate later service packs into A2002 Runtime. NOT A2003, which may or
may not be different.
BUT (because it's not very well documented, if at all) I did it by the seat of
my pants, and there's one recent report (Sover) that it does not work (or not
properly).
My method was to extract everything out of the runtime CAB, replace all the
updated files, then rebuild the CAB. Which is great. Except that, Sover
reported there were some new files with a new SP, and since I don't know how
they "fit", and he reported troubles with the newbuilt CAB, then I can only
say there's no real information on it and if my "seat-of-pants" method does
not work then it doesn't (I DONT work for MS or know anything beyond an
average developer). You can (of course) take the principle involved (replace
files with updated ones) and try it.
Because the runtime keeps changing (SP's, new Access versions), at the very
least my method is specific to a particular version. And that was before MS
provided any method at all (the client had to install your s/w and then
immediately upgrade runtime), but now they at least provide a Chain method.
It's a "safer" method, because it's what MS provides, not lil' ol' me.
What is wrong with an extra 100mB? A CD has 600mB, not to mention DVD. If you
want internet download, then even the original runtime is impractical.
For the record, I think Microsoft SUCKS for not providing updated Runtimes
(they did in A2000). But MS has a bad reputation for not taking the concerns
of Developers and Access Runtime into account. I have fought them for years
with Runtime/PDW and got approximately nowhere, in fact one of their employees
has stated that MS would not bother with improving the PDW because you can
purchase a good installer like www.sagekey.com
I'm not specifically referring to ADP, which I don't know much about.
Please try it (the chaining method) FOR US!!! Tell us whether (apart from an
extra 100mB), the process is in any way upsetting for a customer (NOT you!)
Chris
Disclosure of Interest: I still use PDW not Sagekey, and then in A2000 not
later. I know all PDW's are crap, and that I either put up with it or buy
sagekey. My attitude is that I PAID for PDW (but it seems to cut no ice with
the Supplier!). So far as I know, Sagekey provides updated runtimes, though of
course you still need Office Dev for licensing reasons.
"PBsoft" <info[ at ]REMOVEpbsoft.it> wrote in message
news:875ea355371738c8829ad589808c[ at ]msnews.microsoft.com...
[Quoted Text] > I developer an ADP with Access 2003 and distributed it with a package
created
> wih Package Wizard from VSTO 2005.
>
> When I tried to install the package onto my customer computer I noticed that
> the installed Access 2003 runtime didn't include Service Pack 2003 for
Office
>
> 2003.
> I searched a lot and asked in an italian newsgroup and finally Giorgio
Rancati
>
> told me to visi this page: http://support.microsoft.com/kb/916176/en-us
>
> I red that SP2 files are not included in the package and that I have to run
> a chained installation. This means I have to deploy a package increased by
> 100 MB for each one of my applications.
>
> Do you know any other solutions?
>
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>
>
|
|
Ahhhh...another thought (which may be heretical)
(arrgghhhhh...choking sounds...)
Do you know that the A2000 I currently distribute is SP1? It works fine for me
and I have no known reason to upgrade to later SP's!
Do you NEED a later SP? Usually, you can find on MS website an Excel
spreadsheet of the changes. If you are already running successfully without
the SP, then is there any compelling reason to upgrade?
(Well, sometimes I've found some BAD faults, but not always <g>)
(this is not meant as general advice, OF COURSE it's desirable to upgrade.
However, maybe my app sometimes worked reliably BEFORE further upgrade was
available)
Chris
|
|
|