Code:
the frontend? really only needs plate no. & service\rego dates to function, it would be good if the (hidden) next service date appeared here also (can use the brake start date)
I see your services table contains service info, and car info! In principle, this is a bad solution. We can assume, that a customer can have more than one car.
So either you have a single row for every car this customer has in your services table, and the service info for this car is owerwritten every time the car is serviced - i.e. you'll have no history of services for any car;
Or you have several service rows for every car, where the same car info is entered repeatedly (a no-no for relational DB!).
And with both cases, the date of next service for which car, of several this customer has, must be displayed on customer form? There is no way to do this in a way which covers all possible situations!
With normal relational DB design, you need:
a table where all customers are registered;
a table where all cars owned by customer are registered;
a table, where all services made/planned for specific car are registered (You make service for car, not for customer! Services for customer are made by entirely different kind of firms
- unless your customer is a robot
)
Code:
i have tested & it shows the next service date on the customer-details table after email sending automatically
This means, the procedure which sended the mail out, also updated the services table, and entered the date of next service there!
Code:
but after the new skin, im not sure if it is doing the same as the old database
Depends on how much of code you did take over from old version mail sending procedure, and how well is it working with new version!