SOLVED

Access VBA error - Started with "runtime error 7 out of memory" now Access crashing without error

%3CLINGO-SUB%20id%3D%22lingo-sub-1452630%22%20slang%3D%22en-US%22%3EAccess%20VBA%20error%20-%20Started%20with%20%22runtime%20error%207%20out%20of%20memory%22%20now%20Access%20crashing%20without%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452630%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EI've%20got%20a%20subroutine%20in%20Access%20365%20vba%20which%20has%20been%20working%20fine%20for%20a%20few%20years%20and%20this%20morning%20threw%20an%20%22Run%20Time%20error%20'7'%3A%20Out%20of%20Memory%22.%20I%20have%20the%20same%20routine%20running%20over%20several%20windows%2010%20pcs%20(all%20producing%20an%20excel%20workbook%20for%20different%20people%20all%20at%20the%20same%20time)....%202%20pcs%20still%20work%20the%20rest%20-%20including%20the%20PC%20where%20I%20created%20the%20accdb%20file%20are%20throwing%20the%20error.%20I've%20done%20some%20tracing%20and%20now%20in%20the%20dao.recordset%20when%20I'm%20referencing%26nbsp%3B%20rs.Fields(counter).value%20what%20is%20being%20returned%20is%20rs.Fields(counter).Name%20for%20a%20few%20fields%20and%20then%20access%20crashes.%20and%20what%20appears%20in%20the%20cells%20are%20not%20numbers%20which%20I%20would%20be%20expecting%20-%20either%20the%20field%20name%20appears%20or%26nbsp%3B%3C%2FP%3E%3CTABLE%20border%3D%220%22%20width%3D%2264%22%20cellspacing%3D%220%22%20cellpadding%3D%220%22%3E%3CTBODY%3E%3CTR%3E%3CTD%20width%3D%2264%22%20height%3D%2221%22%3E%EA%BD%B8%EA%BA%88%E7%BF%B9%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3EDoes%20anyone%20have%20any%20ideas%3F%20where%20I%20can%20go%20to%20next%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1452630%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452659%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20VBA%20error%20-%20Started%20with%20%22runtime%20error%207%20out%20of%20memory%22%20now%20Access%20crashing%20wi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452659%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F694655%22%20target%3D%22_blank%22%3E%40graemelever%3C%2FA%3E%26nbsp%3BUnfortunately%2C%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fall%2Fmicrosoft-access-event-procedure-crashes-database%2F0b7d6854-fa91-45ef-a42f-0f0e0c02d5dd%3FLastReply%3Dtrue%23LastReply%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20a%20bug%20has%20been%20identified%20in%20a%20recent%20update%20to%20Access%3C%2FA%3E.%20Scroll%20down%20the%20linked%20discussion%20for%20the%20explanation%20from%20the%20MS%20Access%20Team%20PM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20build%202005.%20If%20that%20is%20the%20version%20you%20are%20now%20using%20and%20which%20is%20throwing%20these%20errors%2C%20you%20should%20roll%20back%20to%20the%20prior%20version.%26nbsp%3B%20If%20that's%20NOT%20the%20problem%20in%20your%20case%2C%20perhaps%20a%20compact%20and%20repair%20will%20clear%20the%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452793%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20VBA%20error%20-%20Started%20with%20%22runtime%20error%207%20out%20of%20memory%22%20now%20Access%20crashing%20wi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452793%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20-%20I%20thought%20it%20was%20going%20to%20be%20update%20related%20(I%20was%20fearing%20the%20worst%20and%20thinking%20I%20had%20a%20massive%20corruption%20somewhere)%20-%20I've%20followed%20you%20lead%20and%20i'm%20back%20up%20and%20working%20again.....Thanks%20Heaps!%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46682%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1453613%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20VBA%20error%20-%20Started%20with%20%22runtime%20error%207%20out%20of%20memory%22%20now%20Access%20crashing%20wi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1453613%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F694655%22%20target%3D%22_blank%22%3E%40graemelever%3C%2FA%3E%26nbsp%3BCongratulations%20on%20solving%20the%20problem.%20Continued%20success%20with%20your%20project.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi

I've got a subroutine in Access 365 vba which has been working fine for a few years and this morning threw an "Run Time error '7': Out of Memory". I have the same routine running over several windows 10 pcs (all producing an excel workbook for different people all at the same time).... 2 pcs still work the rest - including the PC where I created the accdb file are throwing the error. I've done some tracing and now in the dao.recordset when I'm referencing  rs.Fields(counter).value what is being returned is rs.Fields(counter).Name for a few fields and then access crashes. and what appears in the cells are not numbers which I would be expecting - either the field name appears or 

꽸꺈翹

Does anyone have any ideas? where I can go to next?

3 Replies
Highlighted
Best Response confirmed by graemelever (New Contributor)
Solution

@graemelever Unfortunately, a bug has been identified in a recent update to Access. Scroll down the linked discussion for the explanation from the MS Access Team PM.

 

It's build 2005. If that is the version you are now using and which is throwing these errors, you should roll back to the prior version.  If that's NOT the problem in your case, perhaps a compact and repair will clear the problem.

Highlighted

Thanks - I thought it was going to be update related (I was fearing the worst and thinking I had a massive corruption somewhere) - I've followed you lead and i'm back up and working again.....Thanks Heaps! @George Hepworth 

Highlighted

@graemelever Congratulations on solving the problem. Continued success with your project.