Hi Tom; 1) This is not a problem if you allow customers to do their on updates by allowing access to the base system or sending them it to them on a thumb drive, or allowing them to upload the base system via FTP, or some other mechanism. 2) This is always a problem that requires structure from the beginning. If they are changing your live programs, forms, and whatever in their live account then who knows what is custom and what is original. You have setup up files where they can import the original program and modify to their hearts content, but the system knows what to execute by cataloging over the original or modify pointers. This is not something that can be solved by XLr8Installer from your end. Your client would have to it's own custom install script to run after they have run you regular install script. 3) You install your new live code on the customers test account. This allows your customer to test and import their changes until the system is ready to go.
Regards, Doug www.u2logic.com "100% Web based applications solutions too" On Thu, Jun 16, 2011 at 11:28 AM, Tom Whitmore <[email protected]> wrote: > Thanks Doug, > PRC does a great job of tracking what needs to go where, as we pack up the > update. The problems we are currently having are > 1) our customers want updates after their business hours (read late into > the night) > 2) our customers have custom code > 3) our customers would like to be able to test before going "live" with the > update. > > Putting the update in an isolated environment, and letting them "push the > button" to install the code, I believe, would address these issues. > However, there are so many factors involved, we want to make sure we have > identified the gotchas that others have come across. > Tom _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
