Hi Randy,

The first major issue is that IntelliSense does not work within a With...EndWith Block - that is a major pain. Here is another nit - that may have more to do with strong typing than anything else. Specfically, I cannot create a property AS a specific object type. Therefore, if I write something like THisform.MyObject. - it would be great if the MyObject Property could be declared as a given type. Perhaps it could be done in code - but that would require access to the constructor - which we don't get in the graphic designers.

To be fair - I tend to lump it all as IntelliSense when much of what I complain about deals more with code completion than anything else. The ability to have abbreviations expand is a nice feature - and I use that for comment blocks.

HTH

< JVP >




>>>>>>>As for intellisense, I turned it off because it does not work in a way that is close to being correct. Where in VB 6 and in .NET - it helps you - the VFP 7 implementation is a hack - functionality kludged up and layered on an existing code base - and as a result - is a liability more than an asset.<<<<<
>
>John, can you give us more insight to some of the problems you are having with IntelliSense. We have already added some nice improvements for Europa, but are always looking to improve our IntelliSense model.
>
>As for our implementation, we have given product demos of our IntelliSense architecture to a lot of teams here in the VS division since many consider ours to be the best, most extensive of all the models currently available. In fact, you may likely see some Fox-like IntelliSense features in future versions of VS.
>
>Randy