Empty table problem

From: Karl Thompson (KarlThompson_at_yahoo.com)
Date: 10/29/03 

Date: Tue, 28 Oct 2003 18:25:16 -0500

D7 Enterprise, MS Access, DAO 3.6

This code existed in the application prior to converting it to ADO

  {-history table needs to be empty}
  while NOT( FHistory.Eof ) do
    FHistory.Delete;

Now, about 1 out of every 4 times these lines execute, we get this error:

"List Index Out of Bounds (-1)".

Can someone explain to me why? And if it's coded wrong, why only one out of
four times?

Also, interestingly (at least to me) the error never occures when we are
tracing through these lines of code. Rather, it will only occure if we step
over the method call which contains these lines.

FYI - the table has no default values.

(I guess we'll change this to a delete query, but we aren't sure why we
should have to.)