I have been working on a customized screen which includes many data
controls.  When I attempt to load another form (which also has MANY data
controls), I get this error.  I have found that if I close the recordsets
before enabling the other form, I was usually able to load the other form
without any problems.  (I assumed the problem was due to the fact that the
second form was loading before the current form was UNLOADED, meaning the
data controls [and their respective tables] from the current form were still
open.)

Unfortunately, I have now encountered this same error even though I have
closed all the recordsets before loading the other form.

In reading through articles in the knowledge base, I came across several
similar scenarios, although they were regarding VB3.0 and revolved around
TRANSACTIONS.  (Refer to Article ID:Q116034)
http://www.*-*-*.com/

Is there a way for me to increase the database engine's workspace without
requiring tremendous memory/hard-drive resources from the computer running
the application?  And how do I go about accomplishing this?  I am not
(currently) using the ODBC, only the Jet.

I am not clear as to what is WRONG and would like some advice.  Thank you in
advance for any help you can offer.