>
I'm not sure why this is the case, since RV's are, by your own post, a SPT wrapper (even if it's only an incomplete one). The locking issue brought up can be fixed by a local DBC container and is even a issue with large two-tier applications.
>

I don't really see what the issue with DBC Locks is... For me, the locking issue, whatever it happens to be is bound to the DBC. And, with that in mind, it is an immaterial issue since I don't use DBC's in C/S apps...



> If it's an issue with both, how can this be an argument against RV's?


It is more of an argument against anything that renders data directly to a cursor as opposed to an object. With that in mind, because RV's and SPT both use the VFP cursor structure, it is indirectly an argument against RV's and a direct argument against SPT. With respect to n-tier development, the best mechanisim of choice IMO is either ADO, or perhaps XML to some degree...