>- getting data from a remote data (SQL Server) into a "cursor" (what you referrred to as SQLLite).
>- be able to bind "one record" of this "cursor" to a bunch of controls (text boxes, check boxes, etc).
>- when user clicks on Update/Save call "TableUpdate()" and the remote data (SQL Server) is updated from the "cursro" (being it SQLLite or dataset or something else).
>
>
>Strongly-type datasets do 90% of that, plus they give you Intellisense on the columns in the datatables.
>I think of a datatable in a dataset as a cursor.
>The last one, TableUpdate is there in datasets but it seemed kludgy to me, so I wrote my own method that generates SQL code to save any one row from a strongly-typed dataset datatable to the server.
>
>Many people use data objects the same way, but I cut my teeth on datasets so I stayed with them.
>
>
That is my point; I want TableUpdate in .net not to be kludgy but as practical and easy to use as in VFP <g>.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
