access2007, intermittent problem
error - There isn't enough memory to perform this operation

a form with unbound textboxes to enter search criteria
a query that is really an sql server view
a command button that
builds SELECT string into strSql
and executes the following

Me.RecordSource = "SELECT * FROM qrySelectContact WHERE 1 = 2" '
fails here
DoEvents

Me.RecordSource = strsql
DoEvents
If (Not (Me.RecordsetClone.EOF)) Then
Me.RecordsetClone.MoveLast
DoEvents
Me.RecordsetClone.MoveFirst
End If


in order to duplicate the problem I put the above in a loop, FOR N = 1
TO 10000
after 8111 iterations, it fails with the error

further iterations will also fail

if I flip the form to design view and back to form view, the test will
run again
for another 8111 iterations - why always the same number of
iterations ?

obviously some resource isn't been cleaned up, but what ? how ?

Roger <lesperancer (AT) natpro (DOT) com> wrote in
news:01b74c12-b7fc-4240-a6b5-5e1f783feb37 (AT) c13g2000prc (DOT) googlegroups.co
m:

Is there some reason you care that an unrealistic test that is
nothing at all like anything that will ever happen in an actual
deployed application is failing?

That is, what caused you to feel testing in a loop was useful?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Jan 26, 3:00*pm, "David-W-Fenton" <dfas... (AT) dfenton (DOT) com> wrote:
the application is run using the access runtime, so the best I can do
is log errors
having logged a user error and localizing it to the above VB, I was
trying to duplicate the problem
since it is simple code that runs most of the time, I decided to loop
it in an attempt to find the problem
I kept increasing the iteration count, until I got the 'memory' error,
which is not the original error that was logged

so now I've got 9-lines of VB that should never fail, failing with two
different errors
one intermittently and one at iteration 8111 of a loop

I will add more logging to narrow down the exact line of failure

On the workstations showing the error, was the Access application running
for a long time? as in days. Or, did they run some functions that moved
large amounts of data? I once saw this type of error while trying to archive
3 or 4 years of data from 1 BE to a 2nd. I ended up breaking the queries
into steps and restarting Access after each move was completed.






"Roger" wrote in message
news:01b74c12-b7fc-4240-a6b5-5e1f783feb37 (AT) c13g2000prc (DOT) googlegroups.com...


access2007, intermittent problem
error - There isn't enough memory to perform this operation

a form with unbound textboxes to enter search criteria
a query that is really an sql server view
a command button that
builds SELECT string into strSql
and executes the following

Me.RecordSource = "SELECT * FROM qrySelectContact WHERE 1 = 2" '
fails here
DoEvents

Me.RecordSource = strsql
DoEvents
If (Not (Me.RecordsetClone.EOF)) Then
Me.RecordsetClone.MoveLast
DoEvents
Me.RecordsetClone.MoveFirst
End If


in order to duplicate the problem I put the above in a loop, FOR N = 1
TO 10000
after 8111 iterations, it fails with the error

further iterations will also fail

if I flip the form to design view and back to form view, the test will
run again
for another 8111 iterations - why always the same number of
iterations ?

obviously some resource isn't been cleaned up, but what ? how ?

On Jan 27, 6:10*am, "Ron, paii" <n... (AT) nomail (DOT) com> wrote:
the error above occurs on a one-user development server, within
seconds of opening access and clicking the button

the original problem occurs on citrix servers, where users are logged
off after 3 hours of inactivity (usually nightly) and when they log in
they load a fresh, new copy of the application

Roger <lesperancer (AT) natpro (DOT) com> wrote in
news:30dc40ed-5199-4abb-a8f1-d7cbb3bc09fe (AT) o14g2000prb (DOT) googlegroups.co
m:

You're saying that a user using the deployed runtime app ran the
code 8111 times? That seems impossible to me. That is, it seems to
me that you're testing something different from what is producing
the actual error. You may be thereby producing the same error, but
that doesn't mean you've identified the cause of it.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/