Rick Schummer wrote: >>> I suppose you could use Stephen Settimi's approach in EXCLUDING almost >>> EVERYTHING basically and >>> > referring to it in code...<< > > Yes, this definitely defeats the caching problem, but now you are managing > the release of source > code to production instead of APPs. You really only need one EXE and just > deploy the source > directly. Otherwise you have to manage one EXE, multiple APPs, *and* the > source code. This by > definition defeats one big benefit Bill Anderson discussed, which is the > reduction of system > testing. In fact, taking this approach increases the need both internal > system testing and customer > acceptance testing. > > Worse, it also exposes the source code to "unauthorized" changes by anyone > with a copy of VFP. Of > course it depends on the circumstances with the customer, but I think this > opens up a serious can of > worms for most deployments outside of an internal IT department and maybe > some Web sites. > Excellent points. When I did this before, it was as an employee back in the 90s for an internal system and it worked well. But you're right...for external clients, this might be something to certainly avoid!
> Interesting discussion for sure. > Yes! Sometimes we get some good ones here. <g> -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
