Record Is Deleted ?

[McHenry]

I have a simple A2K database.

5 tables and two select queries

I am unable to change one of the queries as whenever I attempt to save the
changes I am presented with the error message "Record Is Deleted". Even if I
simply open the query in design view and click save without making any
changes I receive the error.

Each one of my tables I can change and save with no problems
My other select query I can change and save with no problems


Help !

 

[Allen Browne]

This sounds like a corruption in the database. The problem could be caused
by several things, such as:
- Name AutoCorrect,
- an index of the table,
- a problem with the query,
- code/reference problems.

Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | 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

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, 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

 

[McHenry]

Allen, many thanks from Attadale !!

I actually solved it, stumbled across the solution...
I had a field in the query by the same name as the query... simply renaming
the query solved it and if I change the name back the problem returns !!

Wierd !

 

[Allen Browne]

Thank you for posting the solution.

That's intriguing. I tried to duplicate it in a simple query without
success, but I guess it could be a factor if the query engine misunderstands
the name.