PIEBALDconsult wrote:
That's a big reason not to use stored procedures.
Not really. The user can just as easily go in and update the tables without.
PIEBALDconsult wrote:
At best you could have a written agreement that clearly states what happens when they screw up the system.
Thats a more common way. At the end of the day, if the database is on your clients server, there is very little you can do to stop them screwing it up, so having a good, watertight, written agreement of responsibilities is probably the best way - if they are fully aware of the consequences then they probably won't.
Bob Ashfield Consultants Ltd Proud to be a 2009 Code Project MVP