Hi Zhu,
Thanks for your answer, I have marked it as verified, however it's not really a solution to the issue.
On your link, you state that setting the editable property to be false will mean that new records cannot be edited, and that when opened in read only mode, the edit button cannot be used to enable editing. This does not resolve the issue.
I find it unbearable that in 2023 we are still living with a system where accidental changes can be made to data, by anyone with write permissions on the table.
I've done a lot of searching and found many others who have made the same complaint. Many of the responses to them say things like "tell your users to be careful"... My users are very careful, but accidents happen. My users should not need to be careful. If the pages opened in read only mode and could only be edited after pressing the edit button, then they wouldn't need to be careful until after they'd pressed the button!
I honestly can't believe it's 2023 and a problem that has caused headaches around the world since the days of Nav1.1 still hasn't been addressed by Microsoft.
I'm now faced with a large bill for development to get this issue sorted, for something that in my mind, and the minds of many others should simply be part of the standard setup.
I will ask the dev team at my support partners whether they can write this as an extension that could be installed on any deployment of BC and then see if we can sell this to other companies to recoup some of the costs of doing Microsoft's work for them. I know that 100's if not 1000's of businesses would buy this functionality to ensure the safety of their data.
Sorry to rant, it's aimed at Microsoft, not yourself! :)
Best regards,
Daniel
