Hello Kevin,

I was hoping you would chime in. I am not familiar with the reflections/interface terminology as it relates to .NET, but I gather you are saying there are (at least) two ways to simulate a macro expansion, which is good to know.

Since I know you have done quite a bit with VFP/SQL/.NET I would like your input on the total amount of work/time required to do a avg app in the two tools.

Thanks, hope to see you at the next meeting...

Bob

>Rod (and everyone else)...my two cents on what's been said up to this point:
>
>1) ADO.NET has an equivalent of SCAN FOR....
>
>

Dataview Dv = new DataView(MyTable);
>Dv.RowFilter = "  RowFilter Syntax ";
>foreach(DataRowView Drv in Dv)....

>
>Also....on the note of SELECT....while ADO.NET does not have full-blown SQL syntax, you can establish parent-child relation
>objects and specify PARENT/CHILD in RowFilter syntax. Finally, DataViews in ADO.NET 2005 have the ability to filter dupe rows based on columns.
>
>2) IMO, we should be thinking in terms of VFP/SQL on one side of the ledger and .NET/SQL on the other.
>
>On Robert Pierce's notes:
>
>3) The macro - in the beginning, I used reflection. These days I use interfaces more, so I rely on reflection less. (Robert, on our emails back and forth on speaking at the Philly VFP user's group - this is a major topic point that I would cover. I have a session I've done at Codecamps called "Practical uses of Interfaces".)
>
>More later, but that's what immediately comes to mind....good discussion.
>
>Kevin