>Hmmm..
>
>As far as the object model is concerned, there are some similarities. Direct equivalents? Very few as far a *function* are concerned. For example, both VFP and VB support LostFocus for controls. However, VFP respects LostFocus when ESC is hit and a Cancel button is defined while VB never fires a LostFocus for the current control....little things like that.


Yes, I can imagine that there are many significant differences at the macro (higher context) levels. What I was imagining was more of a micro level comparison. For instance I found what I needed in VB, the IIF function which is very close to the FoxPro IIF function. The first time I looked for it I came up with the conditional compile function (#IF I believe). This threw me off for a day.

That's the type of comparison I'm imagining anyway:

FoxPro Visual Basic

IIF(,,) IIF(,,)
+ (string op) & (string op)


BTW, I was very surprised to see that VB would let me write:

"Summary report at the " & CONTROL.nLevel & " level"

(where CONTROL.nLevel is a numeric field)

Are there some consistent syntax rules in VB that allows this kind of type mixing or is it more hodge-podge?

Curiouser and curiouser!

Peter Robinson