Hi John:

>When you refer to navigational capabilities, I am guessing you are referring to navigating through a recordset that is a subset of records on the server, right? With DBF's, when you open a table, the data is there, and you can freely navigate through everything. This does not fit in the C/S model.>

I realize this but am having a difficult time making higher realize this. My mission was to see if we could use ADO to overcome the limitations of remote views, and "make it work the way the system works now". Presumably for marketing reasons.

Being the lieutenant means I have to accept the mission and not question its rationality. I learned that at Eagle the hard way. Doesn't matter if you bring home the biggest award or write the greatest tool ever, questioning your superiors will get you shunted off into a corner.

>I think I know what you are attempting here. The only way I have found ADO Recordsets to work reliably in VFP is to use client-side recordsets. All client-side recordsets are static. In other words, there is no such thing as a client-side dynamic recordset.>

Better define "reliably" for me. Is there some hidden instability issues we need to be aware of? If server-side cursors are unstable when multiple users are banging away at the system I need to bring it up now, not after we field it.

>While you can manipulate the fields collection by altering the Value Property of each field, directly updating the database through the recordset is loaded with problems. Rather, your best bet is to use the Command Object which references a stored proc. In this scenario, you have a Recordset Object that presents the data to you and a Command Object that handles Update, Insert, and Delete operations. The key is to marshal the field values in the recordset to the parameters collection of the command object. This is a fairly quick task, and one that DataClas 2000 handles for you (see the thread on ADO Management Classes).>

Again, I'm going to need some concrete details here regarding problems with the recordset as a data capture device. BTW I passed the PDF off to my boss and am reading thru it myself. But short of rewriting the app - which is out of the question - I don't see how we can take advantage of it. Also, I'm curious how you deal with passing special characters (single quotes, in particular) thru to an SP.

>ADO works just fine. The issue is in getting folks to not overuse the Recordset Object.>

Right, well, I've already admitted to my density factor being greater than most.
>
>HTH...