If I didn't have to give up all the features I had gotten used to with the other languages, this would be great-- but if I had to choose, I'd choose the features I'm used to, as they increased my productivity and bullet-proofed my code more-- for example, if I can just hit CTRL+SPACE to finish the only possible thing I could mean when typing a variable(I like long variable names for increased readability), it eliminates the possibility that I mis-spelled it. Are there enhancements to VFP's Intellisense for this sort of thing? Is it even possible? I've only been back programming with VFP for 7 working days now, so I'm just finding out these new things they've added since VFP6... :-) Thanks.



>sure, I'd also prefer having properties in mixed case, too. But what you can do in VFP (and not with the other tools) is extending and adopting Intellisense to your needs. That's IMO a great advantage in regards to the other tools. Ken Levy just mentioned a new article about this topic on the MSDN website.
>
>Armin
>
>>>Being serious again - I would really appreciate, if we had mixed case. I don't like having intellisense only really usable for built-in properties and methods. It would save a lot of addditional time when coding.
>>
>>It would be helpful to be able to strongly-type properties as well, so that we can use Intellisense with those as well... The strangest thing with Intellisense, is the way MS completely re-did it for VFP-- it's completely different than Intellisense in VB, VC++, and VS.NET. The shortcut keys are different, some functionality doesn't exist(I always used CTRL+Space to finish my expressions when only one variable name could be intended in VC++ and VS.NET), etc...