I think the problem you have encountered is due to your confusing summation and addition. In this case it is the latter you want.
Normally you would not store the mileage when a service is next due. It can be computed easily in a query. To store the value in a column in the ServiceLog table introduces redundancy, and the consequent risk of update anomalies. Having dropped the LNextDue column from the table, the query would then be:
SELECT
ServiceLog.*,
LMileage + SMiles AS LNextDue
FROM
ServiceLog INNER JOIN Services
ON ServiceLog.LServiceID = Services.ID
ORDER BY
LDate;
In your case you would only store the mileage when a service is next due if you wish to maintain the values in previous rows on the basis of the original service interval, while computing subsequent values on the basis of the amended service interval. In that context Viorel has given you the correct solution.
I notice that the relationship between the tables is not enforced. An unenforced relationship serves no useful purpose. To enforce the relationship select the Enforce Referential Integrity option in the Edit Relationships dialogue.