As Thomas points out, you have to get the data to the control in some manner.

In VFP, we don't think about it: there is no mismatch between a cursor and a control.

Almost everywhere else there is: this mismatch has been labelled an "impedance mismatch" in the literature. An MVC pattern is one way of addressing this impedance mis-match.

There are ways of using oData, which is basically JSON, to make a very lightweight bridge between data and controls. If I were writing my own I'd go this way, probably with some oData-based metadata to handle rules for UI actions and client-side validation.

Hank

>Real basic question....
>Is MVC required in order to use JavaScript?