> > >Attention! > >I loose an hour to debug an apps and when i found >the bug, i decided to publish it. > >I have a long LOCATE cut to multiple lines. ex: > >LOCATE FOR Table1.Field1 = MyVar ; >AND Table1.Field4 = OtherVar ; >AND [...] > >IF FOUND() >[...] > >I change the var name from MyVar to MyNewVar >cut and paste the first line >and place this line in comment to keep >track of the change i have made. > >*(7/9/97) LOCATE FOR Table1.Field1 = MyVar ; >LOCATE FOR Table1.Field1 = MyNewVar ; >AND Table1.Field4 = OtherVar ; >AND [...] > >IF FOUND() >[...] > >I run the apps with no problem, no error messages >but the 'LOCATE FOR' never find anyting! >Even when i change MyNewVar to an explicit value... >Debug,debug,debug... > >HA,HA! >I found the answer, the commented line end with a semicolon (;)! >The comments don't need to start with a * or && if the previous >one is a comment and end with a semicolon. > >Ok, it's not a VFP bug. > >BTW the colored syntax confuse me because it not >show the entire 'locate' command in green (comment color) >it show only the first one (with the * at the begining). > >Be carefull! > >THE END > >:) It's been documented ever since 1991, but we usually fail to RTFM. I've had glitches like that... approximately once a year. The feature I'd like to see is VFP editor being aware of this and painting the comment continuation in comment color. Don't mention FoxWish, they always send you just an automatic reply.