>What they are trying to do is prevent technically-savvy users from changing the data except thru the system. It's a security issue rather than a business logic issue.

I'm going to play dense here so disregard it if you have already had these battles with "them".

SQL Server already has a very robust security model built into it. I don't see the need to add any outside influence. You can limit the access down to the operation on each individual table, view and store procedure using User logins and Roles.

How secure do they need it to be? Or do they want to bypass this because they think this other way is better? While it sounds great for VFP because there is no built-in security, it is totally superfluous for SQL Server.