>It shouldn't be that way - databinding is not rocket science.
>An over reliance on databinding can also constrict the design paradigm. Developers relying on databinding (as those hey-day consultants of the 90's relied on grids [or browse windows]) will end-up with low integration projects (one form - one table).

What are you talking about?

Databinding in a data centric application is a key concept. Nobody wants to manually bind and unbind values to controls manually. It's an error borne process to do this as it usualy involves code in several distinct place that becomes unmanagable very quickly if the number of fields is large.

This process needs to be easy and require minimum of fuss and preferrably be bound directly to the control not some external object.

VFP's databinding is the easiest databinding I have seen and a logical way to do this with minimum effort and maxium results. Sadly .NET's - even VS 2005's implementation - is not nearly as easy to use. It's more flexibly in some ways but requires an separate and a cumbersome UI to perform the binding (or code that it generates). Fortunately it's easy to extend and make it work like VFP.