A97 form blows up, #258

[Salad]

Using A97, SP2, most current jet35.

I have a search form. The op enters an id to search/find. If found, a
data entry form is presented for that id. This form has 7 or 8 combos,
a bunch of textboxes, and some command buttons.

At the client site yesterday the user got a "too many databases open"
after entering a bunch of IDs into the search form. Later that day,
after entering a bunch more IDs, she got an out of memory error and the
combo boxes started asking for a parameter value in the data entry form
for the combo boxes. So I decided to test it out.

On my computer I modified the search form so that it would automatically
work down a list of table ids and open up the data entry form. The data
entry form would open, pause on a timer interval, then close...to be
opened by the next ID from the search form.

I sorted the records for the search form to use in a variety of sorts;
on the ID ascending, ID descending, on status code, and no sort. On
each one of these trials I always get prompted for a parameter for the
combox on the 258th data entry record. Without fail.

Normally the user gets into a form and leaves it. Has one ever
experienced a time when contant opening a form from another form without
closing the calling form many times over creates a problem? Any idea
what would cause my 258th opening of the form make it unstable?

[Tom van Stiphout]

Re: A97 form blows up, #258

On Tue, 11 Mar 2008 17:23:02 -0700, Salad <oil@vinegar.co mwrote:

I'm guessing you have a memory leak somewhere. Check your DAO or ADO
objects. Wasn't there also a problem with checkboxes in A97?
Make sure the value for currentdb.Recor dsets.Count does not increase.
You're not creating a new form object at each invocation, right? Make
sure the value for application.For ms.Count does not increase.

-Tom.

>Using A97, SP2, most current jet35.
>
>I have a search form. The op enters an id to search/find. If found, a
>data entry form is presented for that id. This form has 7 or 8 combos,
>a bunch of textboxes, and some command buttons.
>
>At the client site yesterday the user got a "too many databases open"
>after entering a bunch of IDs into the search form. Later that day,
>after entering a bunch more IDs, she got an out of memory error and the
>combo boxes started asking for a parameter value in the data entry form
>for the combo boxes. So I decided to test it out.
>
>On my computer I modified the search form so that it would automatically
>work down a list of table ids and open up the data entry form. The data
>entry form would open, pause on a timer interval, then close...to be
>opened by the next ID from the search form.
>
>I sorted the records for the search form to use in a variety of sorts;
>on the ID ascending, ID descending, on status code, and no sort. On
>each one of these trials I always get prompted for a parameter for the
>combox on the 258th data entry record. Without fail.
>
>Normally the user gets into a form and leaves it. Has one ever
>experienced a time when contant opening a form from another form without
closing the calling form many times over creates a problem? Any idea
>what would cause my 258th opening of the form make it unstable?

[Salad]

Re: A97 form blows up, #258

Tom van Stiphout wrote:

On Tue, 11 Mar 2008 17:23:02 -0700, Salad <oil@vinegar.co mwrote:
>
I'm guessing you have a memory leak somewhere. Check your DAO or ADO
objects. Wasn't there also a problem with checkboxes in A97?
Make sure the value for currentdb.Recor dsets.Count does not increase.
You're not creating a new form object at each invocation, right? Make
sure the value for application.For ms.Count does not increase.
>
-Tom.

Hi Tom:

In both Search and DataEntry forms I debug.printed
currentdb.Recor dsets.Count
application.For ms.Count
and recset count was always 0 and form count was 1 from Search and 2
from DataEntry.

I started slashing/burning calculated controls, then code, and my count
of opening the DE would increase...slig htly...but would still crash and
I'd still be prompted to enter a paramerter statements from one/more
of the combos.

I then kept opened entry form as original and deleted all combos. Some
combos were predicated upon the value of a master combo; display the
customer combo then display other combos for the contacts of various
contact types based on the customer ID. When I deleted all combos I was
able to enumerate thru the entire list.

Maybe my stress test stressed Access a bit too much by opening/closing
the form quickly. I've looked at the combos...all straightfoward
Select Custemer, custname from Customer Where CustType = 'C'"
and the contacts
Select ContactID, ContactName from Contact where CustomerID =
Forms!Form1!Cus tomerID

If I deleted all the combos based on a master combo list (contacts) and
kept just the main combo (customer), it would still freeze about 2/3
thru the list.

At this point I don't know if I have a memory leak. I set a
timerinterval in the search form. I have a checkbox in the search form.
If false, set to true and open form. Every second check and see if
true or false. In the DE I set the flag to false in the Close event.
Maybe the form wasn't entirely removed from memory when the search form
opened the entry form again...even tho the form/recset counts didn't
show a problem.

There's not much I can do about the combos. Thanks for response.

>
>
>

>>Using A97, SP2, most current jet35.
>>
>>I have a search form. The op enters an id to search/find. If found, a
>>data entry form is presented for that id. This form has 7 or 8 combos,
>>a bunch of textboxes, and some command buttons.
>>
>>At the client site yesterday the user got a "too many databases open"
>>after entering a bunch of IDs into the search form. Later that day,
>>after entering a bunch more IDs, she got an out of memory error and the
>>combo boxes started asking for a parameter value in the data entry form
>>for the combo boxes. So I decided to test it out.
>>
>>On my computer I modified the search form so that it would automatically
>>work down a list of table ids and open up the data entry form. The data
>>entry form would open, pause on a timer interval, then close...to be
>>opened by the next ID from the search form.
>>
>>I sorted the records for the search form to use in a variety of sorts;
>>on the ID ascending, ID descending, on status code, and no sort. On
>>each one of these trials I always get prompted for a parameter for the
>>combox on the 258th data entry record. Without fail.
>>
>>Normally the user gets into a form and leaves it. Has one ever
>>experienced a time when contant opening a form from another form without
>closing the calling form many times over creates a problem? Any idea
>>what would cause my 258th opening of the form make it unstable?

[Tony Toews [MVP]]

Re: A97 form blows up, #258

Salad <oil@vinegar.co mwrote:

>Normally the user gets into a form and leaves it. Has one ever
>experienced a time when contant opening a form from another form without
closing the calling form many times over creates a problem? Any idea
>what would cause my 258th opening of the form make it unstable?

I had a similar problem in A97 quite a number of years ago. Thus I don't recall the
details. The solution was make non visible the called form and thus return back to
the calling form. Then when they opened the called form it made it visible. I
vagully recall I had to set some variables to null or 0 but otherwise that solution
worked.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at

http://www.granite.ab.ca/accsmstr.htm

Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/