Access crashes when entering new record

%3CLINGO-SUB%20id%3D%22lingo-sub-1974646%22%20slang%3D%22en-US%22%3EAccess%20crashes%20when%20entering%20new%20record%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1974646%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20entering%20a%20new%20record%20the%20form%20refreshes%20by%20updating%20the%20screen%20and%20if%20on%20the%20child%20side%20the%20record%20isn't%20found%20the%20program%20aborts%20and%20requires%20a%20resave.%20I%20don't%20know%20how%20to%20fix%20this%2C%20it%20has%20just%20come%20up%20in%20the%20last%20year.%26nbsp%3B%20Any%20help%2C%20comments%20are%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1974646%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1976108%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20crashes%20when%20entering%20new%20record%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1976108%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F812735%22%20target%3D%22_blank%22%3E%40Laura_Conti%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20last%20year%3F%20That%20sounds%20like%20an%20on-going%20problem%20that%20must%20not%20come%20up%20often%20enough%20to%20have%20required%20being%20addressed%20yet.%3C%2FP%3E%3CP%3EYou%20mention%20a%20%22child%20side%22.%20What%20does%20that%20mean%3F%20Please%20explain%2C%20in%20detail%2C%20the%20form%20and%20the%20controls%20on%20it%2C%20i.e.%20cbo%20boxes%2C%20subforms%2C%20etc.%20What%20tables%20are%20actually%20involved%3F%20What%20does%20the%20child%20side%20have%20to%20do%20with%20it%3F%26nbsp%3B%3C%2FP%3E%3CP%3EBecause%20we%20have%20no%20visibility%20to%20your%20computer%2C%20nor%20to%20this%20Access%20relaxational%20database%20application%2C%20we%20have%20to%20depend%20entirely%20on%20the%20information%20you%20can%20provide.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1977998%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20crashes%20when%20entering%20new%20record%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1977998%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3BThank%20you%20for%20your%20reply%2C%20I%20am%20not%20the%20developer%2C%20we%20had%20this%20problem%20every%20time%20attempting%20to%20enter%20a%20new%20record%20and%20therefore%20have%20not%20used%20the%20database%20for%20that%20purpose%20since%20the%20problem%20occurred.%20I%20am%20talking%20to%20him%20about%20answering%20your%20questions%2C%20but%20it%20started%20when%20we%20switched%20to%20Office%20365%2C%20before%20that%20time%20it%20was%20fine%20for%20the%20last%2010%20years.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

When entering a new record the form refreshes by updating the screen and if on the child side the record isn't found the program aborts and requires a resave. I don't know how to fix this, it has just come up in the last year.  Any help, comments are appreciated.

3 Replies

@Laura_Conti 

In the last year? That sounds like an on-going problem that must not come up often enough to have required being addressed yet.

You mention a "child side". What does that mean? Please explain, in detail, the form and the controls on it, i.e. cbo boxes, subforms, etc. What tables are actually involved? What does the child side have to do with it? 

Because we have no visibility to your computer, nor to this Access relaxational database application, we have to depend entirely on the information you can provide. Thanks.

@George Hepworth Thank you for your reply, I am not the developer, we had this problem every time attempting to enter a new record and therefore have not used the database for that purpose since the problem occurred. I am talking to him about answering your questions, but it started when we switched to Office 365, before that time it was fine for the last 10 years.

@Laura_Conti 

Thanks for the additional background. The fact that this started to happen when you upgraded the Access application may have some bearing on the problem, although there is an outside chance it is also a coincidence (they do happen).

So, one thing that might be involved is that there is a problem with the reference libraries used in the VBA modules. Since you didn't create this application and may not be aware of which reference libraries were used, if any, I would suggest you ask the developer about that as well.

And, since it's at least 10 years old, it is probably still an the mdb format. That by itself shouldn't be the issue, but there may be changes such that the macros or VBA used originally don't quite work the same way.