Add a contract clause which details out specific items to which the customer will not have source. For example we have the source to Infor LX. However we know that there are some modules we do not have source for. Generally these are limited to those used to ensure we are not running the code on a machine we are not licensed to. Forbidding the customer from seeing a particular source just because it's proprietary may be a bit harder pill to get them to swallow.
Why does a customer want to see source?
1 - To customize for his business needs.
2 - To protect themselves in case the vendor goes bankrupt and they want to run on a newer system.
Reasons the customer may want the source that the vendor may not agree to.
1 - To continue to use on newer systems, etc without paying maintenance.
2 - To learn the techniques used, which may get leaked out to competitors (your proprietary concern).
So, you're going to have to reach a balance or "deal or no deal" decision.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.