Tamar,
Use gofish4 to check every USE in the processing section- USEing a table or view when the culprit view's underlying dbf is selected can cause an unexpected error that doesn't show up until the requery(). It may be that the record where it breaks does something slightly different and causes this.
On principle I'd make sure virus scanning is off (including on the server) and reindex the table.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
