>I agree with your assessment of Stored Procs. I just wanted to add (for the benefit of others) that using SP's for all data access in a client/server application is considered a "best practice" methodology.

Bonnie,

As we're starting to come around to adding SQL Server/MSDE as a possible back end to our application, I had a question about this methodology.

If one is using SP's for all data access, does that essentially mean you could have at least 3 procs for each table (e.g. insert/update/delete)? For our main app data (i.e. not lookup/reference data tables), I'm sure we could use SQL views and apply the nmethodology to the view, as opposed to each child table.

Just looking for ideas before the big leap..

Laterness,
Jon