I'm just thinking that it may be the only practical way .... After all, there would be a translation layer and it would be difficult to build that into the code behind every control when it could be done once in a DBC as a remote view connection.....

>> Technically, I woould think that a decent fix would involve allowing one to define an ADO connection in CREATE CONNECTION that would translate between DBF cursors and recordsets. This way you could take advantage of data binding and all that and minimize the hassle for upgrading existing apps.
>
>If you're suggesting something like ADO views, where VFP would handle moving records one at a time between a cursor and a record set behind the scenes, I think that would be way cool. But, if we're going to get the ability to bind anything to a record set, then this wouldn't really be necessary. It would be cool to be able to actually define record sets in a DBC though.