>Also keep in mind that the primary reason for using SPs and packages to perform all these functions is for security. In general, security tends to sacrifice some performance. By doing what Larry and I are doing [and others], all we have to grant users is the EXECUTE privilege on our procs and pkgs. This means they have ZERO ability to access and modify data with MS Access, etc., unless they are extremely good guessers at calling these stored procs.
>

Understood, but I've used SPs on SQL Server for all the same reasons for years and never *noticed* such a drastic difference between SP and SPT there (which doesn't mean there wasn't a similar difference that somehow went *unnoticed*, of course).

Thanks,
Kelly