Helmut Kotsch
hkotsch at arcor.de
Mon Sep 13 02:36:43 CDT 2010
Have you checked carefully the validity of the data in the affected tables? I had similar problems in access 2000. In a field that was later on grouped and analyzed there had invalid entries because there was no validity checking during data entry. The later processing depended on either numerical data or the letters "T", "U", "K", "W" or "V". The result was something like too complex query and stopped. It turned out that there have been inputs like "o" or "blank and o" instead of 0. So access didn't know what to do with these items after grouping and gave up without further description. I know that validity checking of data during entry would have prevented this problem but it wasn't there. Helmut -----Ursprungliche Nachricht----- Von: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]Im Auftrag von Rocky Smolin Gesendet: Montag, 13. September 2010 02:09 An: 'Access Developers discussion and problem solving' Betreff: [AccessD] Microsoft Access has stopped working Dear List: I have an app developed in 2003. Works fine. When I run it with Access 2007, one of the reports craps out with the cryptic message Microsoft Access has stopped working (windows is looking for a solution tot he problem - good luck). It does it's repair thing but no cigar. I have no idea where to even being looking. I don't really want to convert this app to 2007 because it's a commercial product and I don't know where it will end up - could be 2003, 2007, or I suppose, 2010. MTIA Rocky Smolin Beach Access Software 858-259-4334 Skype: rocky.smolin www.e-z-mrp.com <http://www.e-z-mrp.com/> www.bchacc.com <http://www.bchacc.com/>