That was my first suggestion, that we create a parallel set of tables, but this 
was not acceptable to them. I will have a meeting tomorrow and if no 
alternatives are agreed on, other than using my tables, I will advise them that 
the maintenance contract will be finished if they modify the contents or 
structure of any tables. Thanks for your input!

----- Original Message ----
From: Stephen Russell <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Monday, November 19, 2007 11:01:49 AM
Subject: Re: Maintenance doubts


On Nov 17, 2007 4:04 AM, Bernardo Stanfield <[EMAIL PROTECTED]>
 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
>

Why not expose a view to him for data?  Have him make his own tables
outside of your app.


[excessive quoting removed by server]

_______________________________________________
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.

Reply via email to