If you imported 4000 records of 1000 characters each, that is 4 MB, which has a long way to go in order to account for 1.2 GB.
Besides the side effects associated with the questions I asked you earlier, here are things I was considering.
1. If you had a JOIN query that was improperly constrained so as to become a Cartesian-product query, you would get a potentially huge number of records. Part of Access query processing includes making a list of records to be joined. An improperly constrained multi-table query could very easily consume a LOT of memory. I'm not sure if that possibility has been ruled out yet. Do you have a non-union query that references two source tables without using a formal JOIN syntax?
2. If you had a lookup field with lots of options, we've seen where they form Cartesian products if referenced in a SELECT clause but not in a WHERE clause. Fortunately, you suggested you didn't have any of those.
3. The "System Resources" problem is hard to pin down because "system resources" is a difficult term to define. (Many things qualify as such.) But the key is that system resources are a limited WINDOWS resource and once they are totally consumed, your app is helpless. Here is a link that might offer SOME help. But no guarantees.
good afternoon readers! I have manual queries which run just fine, but in the following sub, the second append query blows up and give the error 3035 System resource exceeded. :banghead: so I am asking for the experts' help. The data is copied from excel and pasted into a form in table...
www.access-programmers.co.uk
This is a similar (but not identical) article on the "resources" question.
Another thing that can cause the problem is certain virus checkers. We had several computers all bought at the same time, all loaded with same software, except that for some reason, mine did not get errors and the others did. Eventually discovered the only difference was that my computer never...
www.access-programmers.co.uk