>IntelliSense in VFP 9 needs some work.
>
>I typed:
>
>

>WITH This
>
>  SELECT Results
>  SCAN
>
>    IF oApp.   &&<=====  Hit the Dot and IntelliSense opened.
>
>  ENDSCAN
>
>ENDWITH
>

>
>and when I hit the dot, the NotSoIntelligentSense opened with a list of PEM's for the
>class I'm in, not the Application class. The App class has not been instantiated,
>so IntelliSense should not have responded at all. If oApp had been an instantiated object,
>then IntelliSense should have displayed a list of PEM's for it.
>
>The same happens here:
>

>WITH This
>
>  SELECT Results
>
>  SCAN
>
>   Results.Field1 = "SomeVal1"
>   Results.Field2 = "SomeVal2"
>   Results.                      &&<=====  Hit the Dot and IntelliSense opened.
>
>  ENDSCAN
>
>ENDWITH
>

>
>Again, IntelliSense opened with a list of PEM's for the class I'm in, not a
>list of field names, as you would expect. If no table is open, the intellisens should
>not open. If a table IS open, then display a list of field names.
>
>Just my gripe for the day!

You're right. Both VFP and .Net intellisense has some nonsense parts but still better than not to have them at all:)
Cetin