Jim Hardin
08-28-2000, 03:58 PM
Recently applied a Service Pack to VB that causes all upgraded exe's to fail.
We install VB only on a few PCs. The 30 or so PCs that we run the exe's on don't have VB, so they don't get the Service Pack upgrade.
We have gotten by in the past by simply copying the "new exe" to those PCs but this time the Service Pack bit us in the a__!
Short of running an install everytime we make a change, is there any other way to keep up with changes in the Service Packs?
We install VB only on a few PCs. The 30 or so PCs that we run the exe's on don't have VB, so they don't get the Service Pack upgrade.
We have gotten by in the past by simply copying the "new exe" to those PCs but this time the Service Pack bit us in the a__!
Short of running an install everytime we make a change, is there any other way to keep up with changes in the Service Packs?