The query is used as datasource for a form. The problem arises when I want
to delete a record, with a deletebutton on the form.
I first thought that the problem was with the form, but when I try to delete
a record from within the query itself, I have the same problem, so the
problem lies in the query, not in the form...
> Why do you use the outer join? Using the outer join insure you that EACH
> record from PLEEGGEZIN will be in the result of the join, but you only
[quoted text clipped - 30 lines]
>>
>> Marc
Michel Walsh - 15 May 2008 14:47 GMT
Add the keyword DISTINCTROW ? Jet may then be able to trace back which
original row produces each join-result-row.
(that assumes each of the original implied 'table's (queries) in the FROM
clause is already updateable, all alone)
Vanderghast, Access MVP
> The query is used as datasource for a form. The problem arises when I want
> to delete a record, with a deletebutton on the form.
[quoted text clipped - 37 lines]
>>>
>>> Marc
MarcVS - 16 May 2008 08:34 GMT
I tried this, but it didn't help...
Any other ideas would be of great help.
Marc
> Add the keyword DISTINCTROW ? Jet may then be able to trace back which
> original row produces each join-result-row.
[quoted text clipped - 45 lines]
>>>>
>>>> Marc
Michel Walsh - 16 May 2008 15:57 GMT
One of your 'table' is not updateable?
In Northwind, with:
SELECT DISTINCTROW Orders.*, Orders.CustomerID
FROM [Order Details] RIGHT JOIN Orders
ON Orders.OrderID = [Order Details].OrderID
you can add (and then delete) records. So the SQL construction *IS*
updateable. If your statement is not, the problem seems to be elsewhere than
with the SQL statement ITSELF.
Vanderghast, Access MVP
>I tried this, but it didn't help...
>
[quoted text clipped - 51 lines]
>>>>>
>>>>> Marc