Bernardo Stanfield wrote: > I have a client who wants to develop his own system that will interface with > the one that I have provided and for which I have a maintenance contract. He > tells me that he will need to write to the tables that belong to my system > and has asked me if thats OK. I feel that if he starts to modify the contents > and/or structure of 'my' tables, I can no longer be responsible for the > integrity of the data in my system. I need to give him my answer and wonder > if anyone has experience to share on this subject. I'm thinking that I will > not allow this and will suggest that if he wants, I can give him a quote on > the source files for my system and he can take over the maintenance. Any > ideas or suggestions will be very welcome. TIA > >
I'd make it crystal clear that any and all warranties are null and void once someone else outside of your organization messes with (that means adding/editing/deleting) any data in your database. You're asking for a maintenance nightmare otherwise, chasing problems that were NOT caused by your software. (That's an extreme negative scenario, and it might not happen....but it could and you don't wanna be on the hook for it.) -- 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: [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.
