>>>I see nobody defended SPT in this thread
>
>I'll jump in here.
>I'm using SPT exclusively in my framework. My users insist on almost every field of every data type on every form being searchable with %, <>, - as a range operator, - as a literal, etc. I created form control and behavior classes that take care of building the strings for SELECT, INSERT and UPDATE and forget about what the underlying table looks like. I created builders that we use to drop controls on forms that automatically set the target table name and field names and the control classes take care of the rest.
>
>If a given form updates more than one back end table, a programmer has to write custom code, but I find that although most forms pull data from multiple tables, the vast majority of adds and updates only go against one table per form. I never even considered CA's for this. Could a CA do this easier without a lot of sub-classing? I'm always open to easier!
>
>Gary
>

Sure they do, but if you already have these classes built for you with the desired functionality, you may just keep them.