Scotto13
asked on
Access Developer Extentions - Package Wizard - Update runtime systematically
I am using Access 2003 Developer Extensions to package a runtime solution for my database. I often come up with changes and would like to deploy them without having to go to each PC. When I have a new version to install, I have to go to the PC... go to the control panel and uninstall the current version... then run through the setup.
Is there a way to set all of this up in a batch file? So maybe the user could run this and have the application updated all at once - without my needing to go and do this on each PC??
Is there a way to set all of this up in a batch file? So maybe the user could run this and have the application updated all at once - without my needing to go and do this on each PC??
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The PDW should build your Runtime install for you. Nelson's solution would simply update the program you provide for use with the runtime (your .mde/.mdb file).
Are these local users, on the same network? Or remote users?
Are these local users, on the same network? Or remote users?
ASKER
Local users on the same network. I don't know what a PDW is. I use the installer that comes with the Package Wizard. I think its MSI.
That's the Packaging and Deployment Wizard (the PDW). It does produce a Windows MSI package.
Are you packaging the Access Runtime along with your developed application? If so, then you would only deploy the package once; afterwards you'd deploy a Patch or Update and doing that is quite difficult - you'd be better off using a suggestion like Nelson. There are other utilities to do this, or you can use a simple batch file to copy your new frontend across the network.
Are you packaging the Access Runtime along with your developed application? If so, then you would only deploy the package once; afterwards you'd deploy a Patch or Update and doing that is quite difficult - you'd be better off using a suggestion like Nelson. There are other utilities to do this, or you can use a simple batch file to copy your new frontend across the network.
ASKER
I'm not getting something... When I make changes to the .mdb, I then package this and it needs to be installed on each PC. Nelson, how does your tool help with this? It seems that it would only work if I had the .exe installed on the network instead of each PC. Is that what you're suggesting I do?
If I use another utility to "copy the frontend accros the network", would this deploy the .exe? Please break this down for me, as I am new to using PWD.
If I use another utility to "copy the frontend accros the network", would this deploy the .exe? Please break this down for me, as I am new to using PWD.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you both for the excellent ideas. I will work on making it happen with my app.
Thanks for the assist. Good luck on your project.
Nelson
Nelson
ASKER
This looks like a great solution, but I am not using a front end, rather I have a runtime that needs to be installed on indivuals PCs. These people do not have MC Access on their PCs. Can this be addopted to manage this?