Hi Will,

>loData = loBusiness.GetDataObject('table_name')
>loDATA.ADD()
>loRS = loDATA.GetRS()
>loRS.ID = lnID
>loRS.Name = lcName
>loData.SetRS(loRS)
>llSaved = loDATA.SAVE()

I like the way you're treating data as an object. That is exactly what we do with our DataClas/VFP product (www.redmatrix.com). You'd be surprised how many people still haven't seen the light in regards to that.

The primary difference between our two approaches is that we're SQL Server exclusive right now. Therefore we can adopt the "best practice" of coding all data access and manipulations (SELECT, INSERT, UPDATE, DELETE) inside of pre-compiled and optimized stored procs on the server instead of using SQL Passthrough.

We've adopted a "best of both worlds" hybrid approach in DataClas/VFP by using ADO and SQL Passthrough for executing the stored procs. We use ADO Command objects when calling Add, Update, and Delete stored procs and SQL Passthrough when calling data retrieval stored procs.

For the lurkers reading this, I'll be covering how to actually code all of this in the SQL Server Development for VFP Developers pre-con at DevCon this Sunday.