This has now happened twice in the last three monthes. It seems that an "assert .f." with an "set assert on" that is placed directly after a "select" or a "go top" can prevent the "select" or "go top" from executing. Of course not all the time, but some percent of the time.

I have just spent some peice of my sanity debugging a problem with my save method not updating all the records in my table. Sometimes it worked, other times it would only update the last record. My entire save method is in a loop with the first three lines of code:

select payment
go top
assert .f.

After the assert .f. put me in the debugger I would pop over to the data session and browse the payment table and sometimes the record pointer was at the top of the table, and sometimes it was on the last record. This drove me crazy and now after taking the assert .f. out, it has worked everytime.

What do you think? Is it me or is it the debugger?

Brenda