Gary,
Problem is that SPT uses ODBC. You can use ADO instead.
Cetin

>>>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
>
>
>
>>>Soykan,
>>>
>>>>would you like to share with me your caBase class ? :)
>>>
>>>My CA classes will be included in an article that I will post sometime soon, but the current version needs some cleanup -- it's very project-specific at the moment.
>>>
>>>I'll notify you here and by email when it is available for download (probably within a few weeks).
>>
>>I see nobody defended SPT in this thread. It seems a bit unfair, after all data processing is supposed to be done on server if possible.