This problem of the record pointer not moving properly (or moving on its own, depending on how you want to look at it), is not solved in VFP 9. I documented and submitted repro code on this, so it's especially frustrating that they didn't fix it. I wonder if all the new testing tools they have been talking about are giving them a false sense of confidence in the product. It could be like people that think their letter is correct if they've run the spell checker, but the person that gets the letter sees "you" when it should have been "your", "there" when it should have been "their", etc., etc. Testing tools can't do it all. But with repro code submitted through the proper channel, I'm not sure why this bug, introduced in VFP 8, couldn't have been fixed. Arrrgghhhh!!!!


>Actually, I didn't word that very well at all, did I? I was referring to inside or outside of the if statement (process the default or not). Still, I didn't word that very well today either, did I? :o)
>
>
>>I think maybe she was just taking a shot (never hurts to try), though it really shouldn't matter where NODEFAULT is placed, as long as it executes (and you wanted it to execute).
>>
>>>Hi,
>>>
>>>>>
>>>it makes a differnce:
>>>

>>>IF expression THEN
>>> NODEFAULT
>>>ENDIF
>>>

>>>>>
>>>
>>>Sorry, I should have said I thought it made no difference where the NODEFAULT is *executed* - Tracy seems to be suggesting that where this happens can be relevant.
>>>
>>>Regards,
>>>Viv