Maybe a few more error handlers in Functions & Subs to display the error on the screen as the user proceeds through the program. One easy way is to stick advancing numbers through the code that the error message can show along with the message. The developer can then look at that actual location...
I would have thought that Alt+Ctrl+Delete would be the only option.
But would you want to tell your client to use that? I always took the view that the less they knew the better and whatever they do you should be in control of anyway.
I see that NS&I are reducing the odds of a win by 5% from April 26 and reducing the interest rate payout from 3.6% to 3.3%.
This is when interest rates are held or rising outside their little world. I don't know about anyone else but I reckon that the prizes started to reduce in 2024 and that...
I often think that your own way of doing most things is the better way.
A bit like other peoples kids, who are always more of a damn nucance than yours hve ever been!
After all of the years using Access, the other day I accidentally dropped on something I had never come across before.
I have always used form variables as memory variables. Mainly just because I can in Access and also so I can easily see them if I need to. I will store what otherwise would be...
I would like to calculate the difference between a field in one record to the same one in the previous record in a datasheet.
basically on the the 1st record I want to show the number of days back to the second and so on
1st record 12/03/26 =2
2nd record 10/03/26 =1
3rd record...