What are some possible reasons for an update query not working
- Thread starter Mitt1
- Start date
You are giving us not a lot of information. A little like: why are birds sometimes not flying... ;-)
You can help yourself by adding a little more information here.
Errormessage maybe? Or more a description what the query looks like and what goes wrong
What I recently did was to change in the query builder the "update" to "select" and checked when and why it was not possible to add or change values.
Start first with the most simple query you can think of and increase slowly the complexity until the query fails to change values (recordset not updatable message if I am not wrong)
Or the other way around: take away parts of the query until the query is working normal.
Simplify to find the culprit
You can help yourself by adding a little more information here.
Errormessage maybe? Or more a description what the query looks like and what goes wrong
What I recently did was to change in the query builder the "update" to "select" and checked when and why it was not possible to add or change values.
Start first with the most simple query you can think of and increase slowly the complexity until the query fails to change values (recordset not updatable message if I am not wrong)
Or the other way around: take away parts of the query until the query is working normal.
Simplify to find the culprit
Gasman
Enthusiastic Amateur
- Local time
- Today, 16:48
- Joined
- Sep 21, 2011
- Messages
- 17,484
I would have thought that the data did not meet the criteria.?
As mentioned change it to a select and see what is produced and then look at what is missed.
I have just had a situation where a query that has worked for the last few years produced errors this year. That was down to incorrect data.
As mentioned change it to a select and see what is produced and then look at what is missed.
I have just had a situation where a query that has worked for the last few years produced errors this year. That was down to incorrect data.
- Local time
- Today, 10:48
- Joined
- Feb 28, 2001
- Messages
- 30,561
If the query is a single-table query with a WHERE clause, the problem can be an overly restrictive WHERE clause that eliminates the whole table.
If the query is based on updating via a JOIN, it is possible that nothing matches the OUTER JOIN requirements.
If you have warnings disabled, it could be a syntax error in the query itself.
Without knowing more about the query and the surroundings, it will be EXTREMELY hard to diagnose this problem.
If the query is based on updating via a JOIN, it is possible that nothing matches the OUTER JOIN requirements.
If you have warnings disabled, it could be a syntax error in the query itself.
Without knowing more about the query and the surroundings, it will be EXTREMELY hard to diagnose this problem.
Similar threads
