[ACCESS] Delete Query Table Join
Solved
artamys
Posted messages
122
Registration date
Status
Membre
Last intervention
-
artamys Posted messages 122 Registration date Status Membre Last intervention -
artamys Posted messages 122 Registration date Status Membre Last intervention -
Hello,
I am making a join query of tables A and B for the common data.
I would like to delete the data from the join query with a delete query, but I get an error message saying that I am not allowed to delete.
There are no issues with post administrator or anything else.
Any idea?
I am making a join query of tables A and B for the common data.
I would like to delete the data from the join query with a delete query, but I get an error message saying that I am not allowed to delete.
There are no issues with post administrator or anything else.
Any idea?
Configuration: Windows Vista Internet Explorer 7.0
5 réponses
no, actually, it's the code that works.
Query No. 6 joins two tables without integrity.
And creating a deletion query based on this query brought up an error message saying that we could not delete the data. In the creation of the query, ACCESS was actually attempting to delete from both tables when it should only delete from one table; I think the error message was related to the fact that Access did not know where to delete the data from? Table 1 or 2?
With the modification of the SQL code as in the code above, there is no longer any issue.
Thank you very much Blux (for this help and all the others...)
Query No. 6 joins two tables without integrity.
And creating a deletion query based on this query brought up an error message saying that we could not delete the data. In the creation of the query, ACCESS was actually attempting to delete from both tables when it should only delete from one table; I think the error message was related to the fact that Access did not know where to delete the data from? Table 1 or 2?
With the modification of the SQL code as in the code above, there is no longer any issue.
Thank you very much Blux (for this help and all the others...)
Hi,
Maybe a referential integrity constraint?
Detail your queries and your tables (primary keys), so we can see...
--
See you Blux
Maybe a referential integrity constraint?
Detail your queries and your tables (primary keys), so we can see...
--
See you Blux
"Fools can do anything. That's how you recognize them"