Hi!

Hmm, you can bind VFP controls to the ADO recordset fields without limitations...

Converting to/from VFP cursors take some time. In addition, you will require to organize updates someway. See my document file 'DCOM Tests' here for some details - I convert there vfp SPT cursor to string at the server side and back to the cursor at the client side using different approaches include XML using Rick's wwXML class.

>What is everyone else doing for n-tier applications? Are you binding your form controls to a VFP cursor (or ADO) after passing XML or ADO recordsets from the biz tier or are you loading the controls VALUE property during form startup?
>
>Bound Pros:
>- the UI is simple, VFP thinks it is using a pure VFP table (instead of a cursor generated from ADO or XML)
>- less work than unbound
>
>Unbound Pros:
>- don't have to work about "automagic" things happening
>
>I am leaning towards bound so far.