Dave, I've implemented a similar scheme (loader concept and numbered executables). Not as fancy, but with the same effect and ease of use. Since I've already done it, no need to test Craig's solution, but will mention a related thing or two I've done:
- in a LAN configuration, only the server is updated from the inet server. Workstations then check the lan server for maintenance releases during login, and take their updates from the server. - I'm unable to run the VFP compile from within the application, so that's still manual, but having run the compile to create the numbered exe, I then use a developer-only screen in the application to view and drive an INNO Setup script, cut a product release record, run VFPCompressions on both the maintenance ccnnnnnn.EXE and new full build, and upload both to the web server. The best part of all this is that a problem can go from being reported to solved, and the fix implemented and distributed at "lightning speed" (hours). This is a major advantage for folks like us. Bill > Craig has a nice article/software on remote application > updating in VFP: > http://www.sweetpotatosoftware.com/SPSBlog/PermaLink,guid,06bb82c3-9e4c- 4048 -9b3b-87cc8579eb59.aspx or http://tinyurl.com/2br4lq Dave Crozier _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
