>>In general SPs just add another layer of complexity of distributed responsibility. Changes to a SP often requires work on the database and the program (sidenote: SPs are not tracked in source control), not seldomly by two different people. This might seriously hinder development in general.
>
>Going further on this sidenote - on one of the projects where we mostly used SPTs, there were about a dozen SPs for critical processes, and the only way to have them in (but not under) source control was to export them one at a time into a file, and have that file, i.e. a copy, in source control.
>
>Now I see how this can be automated, but the automation process has to be started manually, or (if the source control is integrated into VFP's project manager) in a project hook class. Which is also another level of complexity, but can at least be automated.

Interesting thought