Office Corruption may need a reload??

[Guest]

The version of access (office) i am currently running is

Access 2002 (10.6771.7826) SP3

Now the problem I am getting is from running a query , the query gives me
the following default message when run

'Microsoft Access has encounted a problem and needs to close'
Send or dont send info

If I add in calculated fields into the query

example is I have two fields Kilometres and Gallons

and a field at the end dividing them to give me Kilometres per gallon simple
as that.

I am sure it is corruption but I was enquiring if anyone had heard of bugs
.... that can cause this

Regards
Jason

 

[Allen Browne]

Hi Jason

There's a lot of things that could cause this crash, including Name
AutoCorrect, confused data types, bad indexes, and a raft of flaws in JET
such as those related to nulls in yes/no fields and failures executing
subqueries.

The first stage would be to try to eliminate the obvious causes of
corruption. The steps below are a generic approach to doing that. If that
doesn't work, it may come down to analyzing the query itself and any other
queries stacked underneath it.

Generic steps to elimination corruption (in order):

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

Beyond that, post the SQL of the query statement, and any queries it relies
on.

 

[Guest]

Sorry for a delay,

Thought I would post my outcome (thank you for you info)

The crashing in the end was a result of attempting to divide by zero

thanks again

Jai