RE: Package Wizard - Installation and registration of components
- From: "Peter F" <PeterF@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Jun 2005 00:53:05 -0700
....and following this, given that it seems the product does not do what it
claims to and I am considering asking Mr Gates politely to stick his disk
somewhere very dark and intimate, is there in fact a single piece of software
available that will perform this simple task - package a Microsoft Access
application for distribution and have it work?
I have a full version of Visual Studio .NET, which presumably should package
other applications, but purchased the Office Tools specifically for this
purpose.
--
Peter
"Peter F" wrote:
> In attempting to create a distribution package for a pretty "vanilla" Access
> 2003 application (default libraries only) using the PDW I find that, while it
> works ok on machines which have older versions of Access already installed,
> it gives an ActiveX error while running some code on a 'clean' machine
> (untouched by MS Office).
>
> I need to send the application out to computers which are running unknown
> Windows operating systems and having an unknown (and possibly non-existant)
> version of Microsoft Access. Just the stuff that the PDW is supposed to do.
>
> I've been using the Office 2000 PDW, but it doesn't work on XP operating
> systems, so I've upgraded in the perverse belief that Microsoft will in fact
> have improved the product. This doesn't seem to be the case.
>
> I've read the other posts relating to the PDW and note that the Wizard has
> been found to be by no means magical, and the process of picking up the
> references and including them in the package (which in the 2000 version was
> at least transparent) does not always work.
>
> I have seen advice suggesting that any redundant References be removed and
> have done this where possible. I'm certainly aware of what happens when
> Access can't find one of its References, so cutting out any of the components
> which aren't necessary from the install package makes sense.
>
> Given that there are still one or 2 which I can't remove, save by completely
> rewriting my application (the DAO library in particular, even though I will
> have to do it eventually when DAO is phased out), the only solution I can
> think of is to manually add those references into the package.
>
> I have wandered aimlessly in circles down the halls of the Microsoft site in
> search of detail on how to get the PDW to place a library file in a specific
> location on the client machine, and how to then register this library for
> use. Can anyone point me toward a more detailed set of instructions and
> examples?
>
> If I place the .dll file in the Additional Files list it copies the file
> into the program’s installation folder (or a subfolder if I specify the name
> in the Install Subfolder list), but there is no apparent means of getting it
> to place the file in any other location on the machine, such as where it
> would normally reside in. Having to manually create registry keys, when all I
> want is for the wizard to register the damn things seems a bit too much like
> playing Russian Roulette with someone else’s PC for me to want to contemplate.
>
> The old PDW produced, as part of its outputs, this kind of lovely code in
> the Setup.lst file:
>
> [Bootstrap Files]
> File1=@xxxxxxxxxxxx,$(WinSysPathSysFile),,,11/3/98 12:00:00
> AM,101888,6.0.82.67
> File2=@xxxxxxxxxx,$(WinSysPathSysFile),$(DLLSelfRegister),,11/3/98 12:00:00
> AM,22288,4.71.1460.1
> File3=@xxxxxxxxxxx,$(WinSysPathSysFile),$(TLBRegister),,3/31/03 9:30:00
> PM,17920,3.50.5014.0
>
> The new one has no such code. Obviously the old wildcard syntax indicates
> the method of placing and self-registering. I WILL stoop to modifying the
> Setup.lst file if similar code would work, but that surely isn’t the way a
> $500 US piece of software should need to be used, is it?
>
> --
> Peter
.
- References:
- Prev by Date: Package Wizard - Installation and registration of components
- Next by Date: MDE Files
- Previous by thread: Package Wizard - Installation and registration of components
- Next by thread: MDE Files
- Index(es):
Relevant Pages
|
