Re: Packaging wizard - Microsoft Office Access 2003 Developer Exte
- From: "Chris Mills" <phad_nospam@xxxxxxxxxxxxxx>
- Date: Thu, 20 Oct 2005 18:18:18 +1300
My understanding is that the "Access 2000 Development Team" borrowed the PDW
almost verbatim from the Visual Basic product, where it worked adequately (or
so I'm told). That seemed consistent with their desire to "standardise" (eg
"standardising" VBA was undoubtedly a good idea, pity about PDW)
Unfortunately, Access installations are either much more complex, and/or
Access had a better installer with A97 (I think A97 installer was certainly on
the right track). So PDW was left a mess, not much better in later versions.
In fact, an MS involved employee (in one of these newsgroups, though I can't
say more) admitted that there was not much chance of PDW being improved
because there were better 3rd party products anyway (sagekey).
I'm just relating what I know, or think I know. I think MS has been very
slack, but that's just par for the course in MS-Access. Anyhow, not much will
change given the right fuss that has been made at times (besides me), you have
to get used to it. Buy Sagekey or something similar seems to be the advice.
HTH
Chris
(most common alternatives seem to be www.sagekey.com or installer2go, neither
of which I have. But then, to just upgrade a Front-End, I provide a customer
letter plus a folder on the CD and say "just copy over-write the front-end
file")
"FrankSpencer" <FrankSpencer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> Thanks for you view on this. I think the change in method threw me but I
can
> see your argument. The previous version may have been flawed but it was
> easier for the end-user to simply re-run the setup. Being fairly new to this
> can you tell me if it's possible to package so that the user sees options
> such as "Install" , "Remove" and if so what packaging methods I would be
> better off using. The point about re-supplying just the front-end
> application something I hadn't considered as a cleaner option.
>
> "Chris Mills" wrote:
>
> > In A2000, there was a serious danger of installing twice, resulting in two
> > entries in Add/Remove programs and subsequent near-impossibility to remove
> > cleanly. Other than that, it may have worked.
> >
> > I don't have A2003, but it sounds like they attempted to fix that by
requiring
> > prior removal first.
> >
> > It was never a good idea to use PDW to install an upgrade in A2000, when
just
> > copying a front-end file would suffice and avoid all the hassles. PDW
always
> > was a piece of junk, and this is only one of many reasons.
> >
> > What exactly is wrong with removing the old version first? If you want to
use
> > PDW for it.
> >
> > Chris
> >
.
- References:
- Re: Packaging wizard - Microsoft Office Access 2003 Developer Extensio
- From: Chris Mills
- Re: Packaging wizard - Microsoft Office Access 2003 Developer Extensio
- Prev by Date: Re: Office 9 references automatically updated to Office 11.
- Next by Date: Re: Packaging Wizard error -2147221163 more info
- Previous by thread: Re: Packaging wizard - Microsoft Office Access 2003 Developer Extensio
- Next by thread: 0315338
- Index(es):
Relevant Pages
|
