M
Max Moor
Hi All,
I have an Access app I distribute with Access Runtime. I had troubles
trying to customize the packaging wizard, so chose to use a third party
installer (Tarma). My installer package use to work. I install the
following packages, in the following order:
hhupd.exe System Help
mdac_type.exe Data Access Components
vbrun60sp6.exe VB Runtime
OSP.msi System Files
accessrt.msi Access Runtime
Now, on some XP machines, the Access Runtime portion doesn't install.
I found that the installer throws an error saying it can't open the patch
package.
I tracked down Microsoft KnowledgeBase article 295823. It suggests
that there is info left over in the registry from a previous install. On
its advice, I installed and ran the installer cleanup utility. I removed
the Access Runtime entry in the list, and the problem was fixed. So, I
think I'm on to something there.
The problem is that I can't have customers waiting to see if their
installation doesn't work, then having to install the installer cleaner,
etc, etc, etc.
Is there an automatic check & fix I can run as part of my installation
sequence that would detect and fix this problem? Is there something I'm
doing in the sequence above that might be causing the problem in the first
place?
I'm really stuck here. Any advice would be appreciated.
Thanks, Max
I have an Access app I distribute with Access Runtime. I had troubles
trying to customize the packaging wizard, so chose to use a third party
installer (Tarma). My installer package use to work. I install the
following packages, in the following order:
hhupd.exe System Help
mdac_type.exe Data Access Components
vbrun60sp6.exe VB Runtime
OSP.msi System Files
accessrt.msi Access Runtime
Now, on some XP machines, the Access Runtime portion doesn't install.
I found that the installer throws an error saying it can't open the patch
package.
I tracked down Microsoft KnowledgeBase article 295823. It suggests
that there is info left over in the registry from a previous install. On
its advice, I installed and ran the installer cleanup utility. I removed
the Access Runtime entry in the list, and the problem was fixed. So, I
think I'm on to something there.
The problem is that I can't have customers waiting to see if their
installation doesn't work, then having to install the installer cleaner,
etc, etc, etc.
Is there an automatic check & fix I can run as part of my installation
sequence that would detect and fix this problem? Is there something I'm
doing in the sequence above that might be causing the problem in the first
place?
I'm really stuck here. Any advice would be appreciated.
Thanks, Max