>>Having been a xBase developer for a number of years, when I had to do development in Visual Basic I personally found IntelliSense to be a hindrance. I like to work a particular way and IntelliSense will not allow it. I have mixed emotions about IntelliSense for VFP – turning it off is no big loss to me.
>>
>>Working with IntelliSense to me is like the Word Paper Clip trying to interfere with what I am trying to do. Yes, I know how to write a letter. No, I do not need IntelliSense to make a living – and it is an impediment to the way I work!
>>
>>I am glad some developers are taking the time to define this issue. For me IntelliSense will not replace Apple Pie any time soon.
>>
>
>Tom - I see you have strong feelings about this. But nonetheless, let me suggest that you try working with VFP 7's IntelliSense for a few weeks. If you're still uncomfortable then, try turning off Command Completion, but leave the other features on. In particular, it's hard for me to imagine how someone wouldn't find it useful having the PEM's of an object pop up - I know it saves me tons of time trying to remember exact property and method names. Same thing with the Item Tips that show me the parameters for a function or method.
>
>The best thing about VFP's IntelliSense, though, it its configurability. You can fine tune it to give you exact what you want and no more.
>
>Tamar

Tamar;

You are right and thanks for your input. I am "a bit set in my ways" but open to good suggestions.

Something funny about the implementation of IntelliSense in Visual Basic and Visual Interdev - they sometimes (besides being inconvenient to me) do not define a method or property that is available. That has happened several times. At least I can type in the correct code and it runs as it should.

Tom