>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?
>

One single feature makes VFP a hands down choice for me over VB, other things being equal: Inheritance. This one feature can cut app development time to a third of the time it would take in an app without out it.


>VFP is certainly the way to go for a single tier app, but I'm wondering whether n-tier makes sense with VFP.

I think our current issues with ADO are just that... current issues. Robert Green ws overheard telling somebody last night that an OLE-DB provider for VFP data is an extremely high priority. I feel confident that whatever remaining issues there might be that make ADO difficult to use in VFP are being addressed as well.