>>>Really, trust me......I can wait! I am already having way too much fun trying to figure out how to do some of the stuff my users' want without having to worry about typing variables!
>>
>>Worry... what's to worry about. :-) Example
>>
>>DECLARE
>> GLOBAL CHAR PersonEdit *person who modified the record last
>> LOCAL NUM TotalPeople *number of people at dinner
>>END DECLARE
>>
>>The above would make my day. Changing variable types on the fly is akin to the "goto".
>
>I agree with Dorris on this one. I used Clipper 5.x where (according to in-house standards, not required by Clipper) every variable had to be declared.
>Whether or not it was strongly typed was of very little importance relative to the HOURS debugging old code where variables were just 'used' when they were needed.
>
>I try to declare major variables for any programmers unlucky enough to have to work with my code in the future, but I'm grateful I can throw in a
>
>FOR n = 1 to 25
>
>without worrying where n came from and was it a character variable before.
>
>Now MY pet peeve is the need for a form-wide variable. Sometimes it just isn't convenient to use a form property....
>
>Barbara

Barbara....

That's exactly the example I was trying for (having a MAJOR sinus episode going on and the brain is all mucked up). And before everyone starts thinking that I just use variables willy-nilly, I don't. And I try to have the variable name make SOME sense as to what it pertains to, but one of my pet peeves, especially when I have to come in behind someone and clean up code, is having a 26 letter variable name where 3/4 of the letters have absolutely no bearing on what the variable IS. Ok, so I'm exagerating (sp?) a tad, but for me,


FOR ln_arrcnt = 1 to 25 is less readable AND a major pain in the butt when yer having to type it over and over.