Results 1 to 12 of 12
  1. #1
    Lounger
    Join Date
    Jul 2003
    Location
    Phoenix, Arizona, USA
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Find causes Crashes (XP, SP-2)

    When I run Find several times in a row, my access closes and offers to repair the database and send an error report to MS. Is there a way to prevent this?

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Find causes Crashes (XP, SP-2)

    I can't find anything about this. Are you working with very large tables and/or do you have lots of applications open when this happens? It might be a resources/memory problem.

  3. #3
    Lounger
    Join Date
    Jul 2003
    Location
    Phoenix, Arizona, USA
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    No, Access is the only thing running and DB is relatively small. The DB is divided into FE and BE, and the find works OK several times in a row. It appears that about the 3rd time I go back to the beginning of the data during a search is when it hangs for a few seconds and then crashes. Basically I'm search on last name, the form is "Ordered By: Lastname,Firstname", each of those fields are indexed. Also, not sure if this is relevant, the database is recently converted from Access 97, where the find worked flawlessly. Any help would be great. Everyone at my company is experiencing this problem.

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Find causes Crashes (XP, SP-2)

    Some people report problems with converting databases from Access 97 to Access 2000/2002. It seems these can be avoided by creating a blank new database in Access 2000/2002, then importing all database objects from the Access 97 database. Click Options>> in the Import dialog and check all relevant boxes.
    You will have to set startup options in the frontend anew, and if you have code, check Tools | References... There is by default no reference to the Microsoft DAO 3.6 Object Library in a new Access 2000/2002 database, and many Access 97 databases use DAO code.

  5. #5
    Lounger
    Join Date
    Jul 2003
    Location
    Phoenix, Arizona, USA
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    I had an consultant convert my data and they did do an import into a new system. (I'm trying to get hold of them but they haven't returned my calls) I checked the references and added the DAO 3.6, but that didn't seem to help. I noticed that in 97 I had "MS Calendar Control", but couldn't find it in XP. Do I need to be concerned about mscal.ocx? We still have 97 installed on the workstations. I'm new to access so not much help. Could it also be related to the Jet version?

    I really appreciate any and all your help.

    John Brain

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Find causes Crashes (XP, SP-2)

    If you use the calendar control in your database, and want to manipulate it in code, you'll need a reference. It is also possible that the reference isn't necessary; it may have been left in the Access 97 database because it contained a calendar control at some time, but not any more. In Office XP, the path in a standard installation is C:Program FilesMicrosoft OfficeOffice10MSCal.ocx. Anyway, I doubt very much that this is related to Access crashing after a few searches.

    Perhaps others will have better ideas <img src=/S/crossfingers.gif border=0 alt=crossfingers width=17 height=16>

  7. #7
    Lounger
    Join Date
    Jul 2003
    Location
    Phoenix, Arizona, USA
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    I've done lots of research, and it appears the cause is somehow related to sub-forms I'm using. My main form has 6 pages, 3 of which have sub-forms. When pages with sub-forms are deleted, the find works great. Depending on which sub-form I leave in, I can crash the system at different points in my main DB. I inherited this system and am not a power user. Is there a setting for sub-forms I need to adjust if they're empty? Or, do I need to look at code?
    Again, any help is appreciated.

  8. #8
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Find causes Crashes (XP, SP-2)

    It sounds like whoever you inherited the database from was a little weak on subforms. No, there is no setting you can tweak. The only cure is to wade through the code behind both the main form and the subforms and figure out what was left undone in the first place.
    Charlotte

  9. #9
    2 Star Lounger
    Join Date
    Mar 2001
    Location
    Emerald Beach, New South Wales, Australia
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    If you paid the consultant to convert the database I'd say you should look to them for the resolution of the problem. Stop the cheque and they will return your calls soon enough.

    Failing that can you cut down the databse and post it here for all to look at? You may get a solution that way.

  10. #10
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Salem, Oregon, USA
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    Do you by chance print from HP LaserJet printers? We are/were having that issue with intense regularity in Access, and then some of our users started receiving a similar crash message in Word. _If_ it is a printer problem -- the solution is to delete the printer install and reinstall -- that simple. It's worked now for those in our organization who were having Word crashes, and now it is working (hope, hope) for those who were crashing in a particular Access runtime. More information: it seems that Windows XP, or Word 2002, or Office XP, or who knows is _real_ touchy to minor configuration changes made outisde the properties dialog box in the printer folder (although, our configuration was still something other -- done on the network -- which initiated a spate of crashes in Word). I didn't find this on the Microsoft site, but in the HP LaserJet site, and I don't know if other printers are affected. Anyway, it might be a simple thing to try! -- thx
    Pat

  11. #11
    Silver Lounger
    Join Date
    Jun 2002
    Location
    Cheadle, Staffordshire
    Posts
    2,177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    Perhaps a couple of things to look at which may help.

    Dependant what you're searching from (Main form or subform), perhaps you could set focus to a field on the main form first (seems more efficient).

    Compile your code again, compact and repair.
    Set your db to compact on close.

  12. #12
    Lounger
    Join Date
    Jul 2003
    Location
    Phoenix, Arizona, USA
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Find causes Crashes (XP, SP-2)

    (Edited by HansV to provide link to MSKB article)

    Issue Resolved. There was a Requery going on in the subform that apparently went into an infinite loop. Not sure why it only occurred after doing a find. There is an article that discusses this: <!mskb=288374>Microsoft Knowledge Base Article 288374<!/mskb>. I deleted the subform and used text boxes instead. Thank you everyone for all your input and advice. I'm sure I'll be asking for help again.
    John

Posting Permissions

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