Add to that the fact that many databases contain intellectual property, in the form of stored procedures, triggers, etc., and the legal issues can get hairy. Copyrights aside, I don't see how you could stop them from looking at the structures, or how they could force you to document them. Of course, I'm not a lawyer.

As the others have said, you may want to consider consulting and helping with the transition. These types of transitions can take a long time, especially if the users are resistant, and it could fall apart altogether. If it succeeds, then you would be paid for your time, and maybe learn a little about SAP in the process. If it fails, then you'll be there to continue supporting the client.

>I have a long standing client, whose parent organisation is in the process of implementing a complete shift to an "ALL IN ONE" SAP package. I know I will loose this client, they are not happy about it, nor am I but the organisation knows best (apparently).
>
>Anyway, the staff I deal with have now got to specify the SAP system they need. They have asked me to give them a listing of table structures, what each contains and relations between tables.
>
>If I don't do this they will have to make it up (I like the staff, but they are not IT people!). I've pointed out that table sttuctures are an integral part of system design and therefore my copyright, although the data they contain belongs to them. Am I right?
>
>One of my colleagues has suggested charge a sizeable "copyright release fee", I think this would not go down well, but since we are sure to loose them anyway....
>
>Any opinions welcome to try and clarify my mind on what to do!
>
>
>
>Gary Williams.