Van,

<< All I did was editing a local table in a grid. After doing a table repair
in the Manager, I could edit one record in my program and then the same
error came back.

Then I made this change in my program:
EDBSession.ForceBufferFlush:=true;
Now, the error doesn't come anymore. So, that's good, but still I would
like to know why it came before! >>

Did you repair the table in-between turning on this setting ?
ForceBufferFlush shouldn't have any effect upon what you're describing.  All
that it does is ensure that the data is physically flushed to disk at the
Windows OS level, and is separate from ElevateDB in the sense that it
doesn't affect the operation of ElevateDB at all (apart from decreased
performance a bit).

--
Tim Young
Elevate Software
www.elevatesoft.com