>Don't bother commenting until you've tried emulate the problem.


Are You offending me because I tried to help or am I not getting
what You're saying.


>Read the other replies for the solution.


The only concrete thing I see in this task is Barabara's message, but
that's not a solution, it's a workaround. You are not getting closer
to the problem by simply avoiding it.

My

What!!? ... I can't believe this...

was not against You (sorry if You understood it that way) but a loud
screem of astonishment (against MS if towards someone at all) because if this
is really true for normal table operations it would mean I had to redesign
my table-handling.

In order to come closer to a solution (if I am able to find one at all),
I need to know *what* You are (or Your form is) actually doing when the
error occurs. With the information provided so far it would be rediculous
for me to "emulate the problem".

I am guessing that this problem does not occur by simply opening one, two, three
tables. Otherwise I would have ran into this before, and we had hundrets of
threads here dealing with that problem. So the question is,
"What is the constellation that causes the problem?"


HTH