Using Installer2Go

[Jonathan]

I am currently evaluating this installer product as I have
been having problem with using the Office Developer Kit,
Package Wizard and installing successfully on all current
versions of Windows operating system. But am having a
problem on several test sites and I am wondering whether
someone may have a fix for this....

What I want to do is install an Access 2000 application
and Access Runtime. Using Install2Go, the application
seems to install and run on all the MS Windows operating
systems except ME. When installed on Win ME the database
seems to not find a registered object library installed as
part of MS Access, full version or runtime. As a result
the application does not run properly.

Have you got any idea what may be causing this and a
solution?

Alternatively, any idea why Office 2k Developers Kit does
not create a package that will successfully install on Win
2k operating systems?


Thanks
Jonathan Parminter

 

[Scott McDaniel]

I've successfully packaged and deployed to Win2K systems, although not with
the runtime. From various readings in various newsgroups, it appears that
there numerous issues when deploying with the runtime. Many in the
newsgroups advocate the use of the Sage scripts if you are deploying an
application with the runtime ... they're pricey. I use the Inno installer,
which is free, instead of the P&D wizard ... I still run the P&D to make
sure I pick up all the dependancies, then use a standard script in the Inno
installer to generate my package. Since I stopped using the P&D to package
my databases, I've had less trouble and much more control over what, how,
and where things get installed and uninstalled.