Results 1 to 11 of 11

Thread: Access Crashing

  1. #1
    Join Date
    Feb 2005
    Posts
    24

    Unanswered: Access Crashing

    On some of my users computeres they keep getting the following error message. Microsoft Office Access has encounterd a problem and need to close. We are sorry for the inconvienence. This does not happen on all of the computers, and only happens with one database.

    Any ideas?

    thanks
    ryne23

  2. #2
    Join Date
    Nov 2007
    Posts
    93

    crashing

    well it doesnt happen to all but only to those whose database's becomes corrupted

    so the best solution for that would be .. jst create a blank database and import everything from the old database...

  3. #3
    Join Date
    Feb 2005
    Posts
    24

    Access Crashing

    Thanks I will give that a try.

  4. #4
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Does the db crash at the same point every time or is it a totally random crash?
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  5. #5
    Join Date
    Feb 2005
    Posts
    24

    Access Crashing

    At the same point. Usually after the spell checker has ran and then a button is clicked on to continue to the next screen.

  6. #6
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    If you can replicate the problem every time, then you could start "aggressive analysis" -- removing bits of the problem form and retesting until you can isolate the element that is causing the crash. Working on a copy of course.

    Once found you can delete that element and rebuild only that element and see if you can resolve it that way.

    Have you tried the rebuild database suggestion in post 2? If so, what happened?
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  7. #7
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    How large is the DB(without tables) ?
    1.Try to repair it one,two,three,....times
    (My Expierience: sometimes the third is succesfull)
    2.Re-import your DB into new file
    3.Switch compile on demand to OFF
    4.Try to use SaveasText/LoadAsText...
    5.Decompile DB:
    - Backup your DB and desable any startup code
    -create shortcut: Acces_path\myDb1.mdb /DECOMPILE,and start it
    -Save your DB and quit access
    -Start access again, load your DB normally, and immediately compile your project
    -Quit and restart access
    Last edited by pacala_ba; 03-07-09 at 11:59.
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  8. #8
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    Verify your DB:
    ? CompactRepair( "My_path\MyDB.mdb","My_path\MyDB_new.mdb",true )
    -------------------------------------------------------
    if exists Log file (MyDB_new.log)....corruption is there !!!
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  9. #9
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    pacala: see my reply to your other post on "stream has a length of zero!"
    existance of .log does not seem to be a useful indicator of corruption.

    izy
    currently using SS 2008R2

  10. #10
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    izyrider, i know that, you are right.

    Very-Long-code-lines (near Full-line-of-code)
    are POSSIBLE but NOT-VERY-SAFE...
    (expression1:expression2:expression3......)
    i have used them , and allways crashes in ACCESS 2003 (but not in Access2000 !!!) ...
    Now i have shorten them with MZTOOLS , with line separator ' _'
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  11. #11
    Join Date
    Feb 2005
    Posts
    24
    Thanks to everyone for their input. I did find a piece of code tht was crashing the system. Disabled that code and it seems to be fworking good now.

    Once again thanks.

    Mike

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •