>
>My concern so far with ADO, is that I find it hard to trap every error that occurs in VFP because it gives me its native error message and it causes the entire app to close. Unlike SPT, it returns 1,0,-1 which is very easy to trap in code and code management is seamless.
>

ADO/OLE-DB servers an error, which can be trapped in your error handler. With ADO, you have to be careful to trim your strings and respect data-types carefully. There is no reason why you cannot trap errors. For further information on errors, make sure to query the errors collection of the connection object.


>
I didn't know about ADO before until I learned VB. With DE in VB, ADO shape is awesome because you do it visually.
>

The shape stuff is nice. However, for data entry applications and presentation, I don't find it as useful as I thought I might. For OLAP, the shaped recordset is nice for delving into cubes. Other than that, I don't see much use for it. As a way of presenting data, I don't think most users would like it..



>With the significant advantage of ADO over SPT, I am quite pressured to convert our SPT intensive app which we based it on RobertG's 3tier Technical Reference.
>

It depends on what the "significant" advantage is. In a VFP scenario, SPT can render data in a VFP cursor - the power of which cannot be under-estimated. From a stored procedure standpoint, ADO is much easier to work with since you have a parameters collection. In my opinion, a hybrid approach - using both ODBC and OLE-DB is the way to go. Of course, this is what DataClas 2000 does.

Good luck..