Bonnie,

>Well, here's my opinion, FWIW ... I think you should have all access to SQL through calls to SPs. We're in the process of building a new app (although it's not a VFP app, it's .NET) and that's the way we're doing it.
When things change (query requirements, schema changes, etc.) you only have a few SPs to change, which is quite easier than having to re-build your app and re-distribute it.

When things change, it's usually client driven, which means I'll need to change the front end or report in some manner anyway. If the business logic used is unique to that front end, then I've saved development time because i know nothing else makes use of the code and I can take care of the change all in one place.

Here is where the differences in our environment maybe coming into play, as we do nothing but inhouse corporate development. Our system is layed out very granular such that we can deploy updates to small pieces of the system very easily.

>If you decide *not* to go that way, then at the very least you should have all your data access in one tier so that should things change, you don't have to go digging through-out your whole app to find all the places where you used SPT.

We do intend on consolidating all commonly used business logic. Also, we've standardized upon the way we make SPT calls to help deal with that problem of tracking things down.


Thanks for your feedback,
Anthony