paulsteigel
New member
- Local time
- Today, 21:14
- Joined
- Nov 8, 2010
- Messages
- 1
Hi guy!
Wondering a suitable mechanism to keep a mass-deployed application updated using Internet, I am thinking of 2 options (that I will describe briefly below). My application is in mdb format (I don't expect to hide code as I want more curious people access it and revise. My application is for community used and password protected with VBA code, however, password for accessing code is supplied on demand)
Please advice me on what would be best:
1. Create a split front-end with self updating mechanism.
+ Using this, the application will have a core module for removing/Adding of form/macro...
+ By accessing a certain web site frequently (1 check per day), it found a new version e.g a new report, a new form or new cls module. It will download the file (already compressed) to a temporary folder.
+ The downloaded will then be extracted, old module/form will be removed and replaced with the new one.
All such work will be done first before any other work. After the successfully update, the application may require restarting or be ready for use.
[[I tested this method and feel fine with result on my computer/ yet testing on other]]
2. Use a third party FE updater (this is good for copy and replace) and quite abundant out there.
How do you guy think about this? Please advice me.
Wondering a suitable mechanism to keep a mass-deployed application updated using Internet, I am thinking of 2 options (that I will describe briefly below). My application is in mdb format (I don't expect to hide code as I want more curious people access it and revise. My application is for community used and password protected with VBA code, however, password for accessing code is supplied on demand)
Please advice me on what would be best:
1. Create a split front-end with self updating mechanism.
+ Using this, the application will have a core module for removing/Adding of form/macro...
+ By accessing a certain web site frequently (1 check per day), it found a new version e.g a new report, a new form or new cls module. It will download the file (already compressed) to a temporary folder.
+ The downloaded will then be extracted, old module/form will be removed and replaced with the new one.
All such work will be done first before any other work. After the successfully update, the application may require restarting or be ready for use.
[[I tested this method and feel fine with result on my computer/ yet testing on other]]
2. Use a third party FE updater (this is good for copy and replace) and quite abundant out there.
How do you guy think about this? Please advice me.