Seeking T-Shooting Suggestions

[Steven]

I have an Access 2007 application that uses linked ODBC tables to SQL Server
2000. The application has many Access forms, all of which work flawlessly,
except for one mainform with 2 subforms.

The way the mainform with 2 subforms works is that you select a customer
from a combobox on the mainform, and the remaining textbox controls on the
mainform display the customer's info. The 1st subform displays Purchase
History for the customer. The 2nd subform displays Unpaid Purchases for that
same customer. For example, the Unpaid Purchases subform may display info
like the following:

Item Purchase | Balance Due
===============|=============
Product X | $100
Product Y | $200
Product Z | $400

If the customer sends a bulk check for $450, this amount is entered into a
textbox on the mainform. A button is then clicked on the mainform and the
code behind the button allocates $100 to the Product X purchase, it then
allocates $200 to the Product Y purchase, and finallly allocates the
remaining $150 to the Product Z purchase. When done, the purchase of Products
X and Y now appear in the Purchase History subform, and the Unpaid Purchases
subform displays:

Item Purchase | Balance Due
===============|=============
Product Z | $250

Most of the time, this works fine, but every once in a while, ACC2007
crashes. It's a hard crash that leaves me with no other options than to [Send
a Report] or [Don't Send]. Whenever I step thru the code, it always works. I
can never get the crash to occur while stepping thru the code. I've been on
this issue for weeks. I'm looking for suggestions on how to find the cause of
the crash.

BTW, this problem began after I upgraded to ACC2007. Before this, the
application never had this problem in ACC2003. Since these forms were
originally designed using ACC2003, I have completely rebuilt the forms from
scratch using ACC2007, but the intermittent crashing continues. Maybe it is
something in the ODBC that is causing the crashing, but I am at a loss and
looking for any ideas.

 

[Chris O'C via AccessMonster.com]

Make sure track name autocorrect option is turned off.

Make sure the link child field is bound to a text box or other control in the
subform and the link master field is bound to a text box or other control in
the main form, even if they're not visible to the user. In the link child
fields property, put the control's name, not the field name. In the link
master fields property, put the control's name, not the field name.

You have multiple operations to update multiple records as "paid" when the
payment exceeds the amount for 1 purchase. Are these operations embedded
within an explicit transaction? Is this tranasaction timing out?

Are you using runsql or execute for the update queries? Don't use runsql.
When it fails it doesn't tell you.

Is the db file format still an Access 2003 mdb or did you convert it? Or did
you import the objects from the original db into a new Access 2007 mdb or
accdb?

Chris

I have an Access 2007 application that uses linked ODBC tables to SQL Server
2000. The application has many Access forms, all of which work flawlessly,
except for one mainform with 2 subforms.

The way the mainform with 2 subforms works is that you select a customer
from a combobox on the mainform, and the remaining textbox controls on the
mainform display the customer's info. The 1st subform displays Purchase
History for the customer. The 2nd subform displays Unpaid Purchases for that
same customer. For example, the Unpaid Purchases subform may display info
like the following:

Item Purchase | Balance Due
===============|=============
Product X | $100
Product Y | $200
Product Z | $400

If the customer sends a bulk check for $450, this amount is entered into a
textbox on the mainform. A button is then clicked on the mainform and the
code behind the button allocates $100 to the Product X purchase, it then
allocates $200 to the Product Y purchase, and finallly allocates the
remaining $150 to the Product Z purchase. When done, the purchase of Products
X and Y now appear in the Purchase History subform, and the Unpaid Purchases
subform displays:

Item Purchase | Balance Due
===============|=============
Product Z | $250

Most of the time, this works fine, but every once in a while, ACC2007
crashes. It's a hard crash that leaves me with no other options than to [Send
a Report] or [Don't Send]. Whenever I step thru the code, it always works. I
can never get the crash to occur while stepping thru the code. I've been on
this issue for weeks. I'm looking for suggestions on how to find the cause of
the crash.

BTW, this problem began after I upgraded to ACC2007. Before this, the
application never had this problem in ACC2003. Since these forms were
originally designed using ACC2003, I have completely rebuilt the forms from
scratch using ACC2007, but the intermittent crashing continues. Maybe it is
something in the ODBC that is causing the crashing, but I am at a loss and
looking for any ideas.