Yeah, binding directly to ADO controls seems like the way to go. However, by doing that you are replacing the VFP cursor engine with ADO, then why use VFP and not VB? VB has better support for ADO, including a dataenvironment that supports ADO and a much easier way to surface COM events (WITH EVENTS). Since ADO is the way to go, what advantage does VFP as middle tier or 2 tier tool have over VB?

VFP is certainly the way to go for a single tier app, but I'm wondering whether n-tier makes sense with VFP. There will be a follow up aricle to the "Jump Start with ADO" on the VFP website explaining how to use ADO and VFP Cursors togther to make really powerful middle tier components. This should be interesting. I really hope VFP becomes that the best tool for building middle tier components.

Charlie