In a query (or form based on it) I delete a row, but after requery, the row reappears.

[iordanis]

In a query (or form based on it) I delete a row, but after requery, the row reappears without any message telling me that the query is not updateable. The row disappears correctly and all events are fired, but no record gets deleted. My query uses 6-7 linked tables and two outer joins (although I don't know if it matters)



The thing is that if I delete the master record directly from the access table, it IS deleted. So it must be the query. But why is access accepting it for delete, but doesn't delete it?

[Micron]

You referred to events so I take it that you're doing this in code, so post the code (within code tags - use # button on posting toolbar). Or set a break point in the first event and step through (F8) the code and watch how it executes. My guess is that you've disabled warnings or something similar, like used On Error Resume Next.

[June7]

Or provide your db for analysis - follow instructions at bottom of my post.

[iordanis]

I just sent the schema with some data and the query that behaves just like the form itself. Open the query and delete a record. Then requery. The record reappears.


Database1.zip

In order to move on with my project, i have the deletion done by code in the Delete event of my form, which actually deletes the master and detail records (cascaded), but i also get a 3197 error. My app has attached tables (MDE/MDB) and either has the "no locks" activated.

[Welshgasman]

And a 3197 error is?

[davegri]

Delete the circled relationship and the query will delete properly. This view is the relationship view, not the query design view.

Note: This solution is flawed. I could not get it to repeat properly when I came back later to check. My apologies.

[June7]

Nevermind, now I see Dave's response.