Steve Schapel
miscellany at mvps.org
Mon Jul 21 17:06:53 CDT 2008
Dan, You don't need an installer, under those circumstances. The advantages of using something like Sagekey scripts etc are: - avoid conflicts with pre-existing installations of earlier versions of Access - automatically create trusted location for your application - take care of registering add-ons or special fonts or whatnot In the case of an install just for one client, all of these are easily managed manually. Just… 1. Install the Access runtime on the client's machines, directly from http://www.microsoft.com/downloads/details.aspx?FamilyId=D9AE78D9-9DC6-4B38-9FA6-2C745A175AED&displaylang=en 2. Edit the Registry to make the trusted location. (I got a script somewhere to do this.) 3. Install any DLLs etc. 4. Put an applicable shortcut on the desktop. 5. Have a coffee. Regards Steve Dan Waters wrote: > I'm testing an installation package with a bare-bones Access file, primarily > just to test the installation of an Access runtime. The installation went > well, but when I try to uninstall the runtime, it really won't install. > > I removed full office 2003 from my test PC first. I do have admin rights on > the test PC. > > I've heard that using other installer applications do a better job - but I'm > installing the runtime at just one client site. Anyone know what I could > expect to pay for Sagekey? Or other installers? > > Thanks! > Dan