>What I would like to have is the autocompletion of declared variables. I don't >know if it is me that does something wrong but VFP7 does not behave like VB on >this. In VB, you declare a variable and you simply have to type the firsts >letters and press CTRL-SPACEBAR to have a list of choice of auto completion.

You're correct, we don't have this. Because you can extend IntelliSense in 7.0, I'm certain that you could extend it to do this. Anyway, I'll pass it on as feedback.

>Also, suppose I declare an ADODB command object :
>
>LOCAL cmd AS ADODB.COMMAND
>
>cmd.CcommandType = ... I would like to see the same predefined constants that >are available in VB.

Interesting, I believe that there's a bug with this one. If you do
LOCAL rs AS ADODB.RECORDSET

rs.CursorLocation =

you should get a dropdown list of the predefined constants and the number for VFP. I will report the one about the command object and see what's happening there.

>Other point. As I said in another thread, I would really appreciate to get a >list of fields from a specific table. When I type MyTable. ...I would like to >have the same behavior that I find in the command window, that is the list of >fields available for the specified table.

I understand that this could be nice. The issue is here that in a PRG we haven't opened a table so we really cannot do this. The PRG is not live when we do an USE command. You can also do expressions, so this would be too complicated to deal with in the PRG situation.


Anyway, thanks for the feedback. I believe though that, beside your first point, our IntelliSense is pretty complete and the fact that it is completely extensible makes it 1 step above other products that I've worked on. You should take a close look at the extensibility mechanisms of IntelliSense and party on it.

- Ricardo