Simon,

Well, since you've already got stuff in place in SQL Server, I wouldn't move it out of there. Keep it. It probably doesn't cover *every* biz rule anyway, so I'm sure you'll still have stuff to put in .NET biz classes. <g>

~~Bonnie

>I did consider putting this in the OOP category, but it's probably better here.
>
>I have an existing VFP6 application which is forming the functional prototype for my .Net project. All of the data is on SQL Server 2000, and there are stored procedures and triggers to perform a lot of the processing and enforce business rules.
>
>My question is: with .Net, is it better to leave the business logic in SQL, because it is closest to the data, or should I move it to a set of business objects in .Net ?
>
>Thanks for some pointers,
>Simon