>>>>>The print when in a report field said >>>>>>>>>> bill_type <> "ST" >>>>> >>>>>All was well till some rows with bill_type = "STRAP" disappeared and the user complained. >>>>>Yes, I know that's how VFP works, but it's a PITA. >>>> >>>>Stupid question....and this shows how little VFP work I've done in the last 17 years...but isn't there a SET EXACT (or similar) setting in VFP? >>> >>>Yes there is but I used Tore's method when I figured out what the issue was. >>> >>>I'll never get used to the idea that someone would write a language that allowed "STRAP" = "ST" to be true and therefore I'm doomed to make that mistake over and over. >> >>It makes sense when you remember that FoxBase was created as an interactive language, where users were going to be typing in their commands. So a lot of things were optimized to make it easy for the user to type the right thing. In that scenario, having SEEK "ST" (actually, early on, I think it was just FIND ST, without the quotes; not 100% sure, but I think SEEK came later) > >Yes, SEEK came later. > >I thought it was pretty slick back then that you could find all the rows that began with certain letters by setting exact off before seeking. >I just have a hard time seeing how that logic makes any sense in a comparison, hence my occasional blips.
Took me a long time, but I've got NOT (field == var) in my brain as the way to do this now. It's really rare for me to forget.
