Hi Paul

BTW, I posted your comments on the VMP discussion board and Drew replied thusly...

>>When I started using VFP 7.0/Intellisense, I started using the default capitalization from Intellisense. So code that I've written or modified, starting about a year ago, is capitalized differently from the rest of VMP framework code. That's just a capitalization difference, not a style difference.<<


>>
>>In all the years I've been involved with MaxFrame I've looked at much if not all of its code. I've also submitted many enhancements and ideas to Drew. I have no idea what you are referring to here. Every piece of code submitted to Drew is subjected to a process affectionately called Drewizing <g>. He gets the general idea of the submitted code and redoes the code. He gives credit to the originator in the comments of the class/method/prg. Maybe you can provide an example of inconsistency? It would be preferable to show one that makes it difficult to debug, of couse. IMO the code is VERY consistent, but consistency like EVERYTHING is in the eye of the beholder.
>
> I'll see if I can dig up some code in the next few days - I haven't done any development with it in at least 6 months. But, as an example (and maybe it's just me), but it bothers me to read code that changes case. I find it very distracting and harder to follow. This is partially the inconsistancy I'm talking about. The same thing goes for spacing, whitespace, and indentation of code.
>
> I prefer uppercase for VFP code, but our company standard was lowercase. An app I started to work on last year is in lowercase and I've continued to use lowercase even though, at this point, I can change the company standard to anything I'd like. Yeah, maybe I'm just anal about these sorts of things ;-)
>
>Just so I'm clear here, while I'm not a particular fan of MaxFrame, we've got one "big" app written in it (2 years, and at one time 10+ developers - read: expensive...), and another vertical market app. using it. It's a capable framework, just not my cup of tea.