Derek,

>If you hack the vcx file(open as table, edit memo field manually), you can change the method names(PROCEDURE [methodname]) to a mixed-case setup. This mixed case will show up in Intellisense(VFP7 SP1). However, this doesn't help when I hack the table to do this for properties-- they're always lower()'d by Intellisense.

Hacking the VCX may work for methods, but method names may change, new methods are constantly added to many classes, so you'll always have to hack the VCX again.

>Intellisense really is the key part to this horid mess--

I think the bigger problem are the visual tools that store the names in the tables and deal with the lower case names. If all the tools would work with mixed case, Intellisense should be a small problem to adopt. Just my guess - of course I don't know for sure.

>this problem completely negates the increased productivity of Intellisense if you want to create clean, readable code code, as you have to go back and proper-case all your methods, properties, etc. If MS isn't going to give VFP's IDE the proper attention to fix such MINOR code issues, that have MAJOR impacts on the way we work, maybe they should just open up the source so we can fix them(I can dream, can't I?)...

Once owning a Ferrari or Porsche is a dream that is more likely to become true :)) But we may all have a dream ... but I'd prefer the Porsche over the VFP source code <vbg>. Much more fun <g> (especially here on the Autobahn - no speed limit in many places).

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.

Regards,
Armin