Upgrading even if there's another version
Hi all,
#1. I am using Microsoft access developer extentions to package my adp file. Now I package and deploy alot, so now my users need to update alot. How can I customize the windows installer (msi) so that when it installs and sees that there's already another version, then it just upgrades the application. it doesn't return an error that you need to uninstall first.
At the moment it returns an error and tells me that there's another version (old) already installed, I first need to uninstall then try again.
#2 In the user interface. How can I remove the page which asks where to install the application. Users should not be able to install to a diffrent location other than the defualt.
#3 Is it in some way possible to have an form which asks you what your SQL server name is and then writes to the ADP file the sql server name it should connect to?
Ok that's alotta questions, but #1 is the most important at the mo... thanks alot in advance
#1. I am using Microsoft access developer extentions to package my adp file. Now I package and deploy alot, so now my users need to update alot. How can I customize the windows installer (msi) so that when it installs and sees that there's already another version, then it just upgrades the application. it doesn't return an error that you need to uninstall first.
At the moment it returns an error and tells me that there's another version (old) already installed, I first need to uninstall then try again.
#2 In the user interface. How can I remove the page which asks where to install the application. Users should not be able to install to a diffrent location other than the defualt.
#3 Is it in some way possible to have an form which asks you what your SQL server name is and then writes to the ADP file the sql server name it should connect to?
Ok that's alotta questions, but #1 is the most important at the mo... thanks alot in advance
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Bladerun
18 years ago
Posted by:
tjoppie
18 years ago
Well... The setup files are resident in a network share.
My application checks for new updates in sql server when the user opens the application. So when the application sees there's a new version, or his version is old, it runs the setup.exe in the network share.
This is the only way for me as my users have limited pc knowledge and the only way I can be sure that they upgrade is if they don't even know that they're upgrading. [8|]
Got any ideas?
I was thinking of setting the msi to reinstall always, but how do I that?
Thanks
My application checks for new updates in sql server when the user opens the application. So when the application sees there's a new version, or his version is old, it runs the setup.exe in the network share.
This is the only way for me as my users have limited pc knowledge and the only way I can be sure that they upgrade is if they don't even know that they're upgrading. [8|]
Got any ideas?
I was thinking of setting the msi to reinstall always, but how do I that?
Thanks
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.