mannaggia

At first, I had no idea what a lot of the more complex programs did like games. But then I would start to mess with changing some lines just to see what would happen. Change a POKE, or a FOR loop, or a DATA statement. See what havoc I would cause.

As an aside, one thing I disliked, especially seen in the pre-personal computing era, was seeing manuals written in the third person, like “the compiler allows the user to build a program”. Many were written like internal documents to others in the company of the publisher and “the user”, who was the ultimate consumer of the document, was just a bystander.

@johnG I would also point you to my answer on this thread - sharepoint.stackexchange.com/questions/215512/… in regards to whether you want to use the Script Editor web part or the Content Editor web part. The advantage of the Content Editor web part is that you can put your JavaScript code in files stored in a document library (or some web server) instead of in the web part - makes it easier to maintain.

@johnG, if you do a web search, you can find SPUtility.js and SPServices.js. You will also need jquery. Include those on your page. To disable a field like "Customer Name", you use SPUtility.GetSPField("Customer Name").MakeReadOnly(). You don't need to mess with internal names. Same with checking Status and disabling the Approver field. Use if (SPUtility.GetSPField("Status").GetValue() == "Canceled") SPUtility.GetSPField("Approver").MakeReadOnly(); As for checking the security group, that's where SPServices.js can help make things a little simpler calling some of the SharePoint services.

I would consider using the SPUtility.js and SPServices.js libraries. If you are concerned about future proofing, one would assume the maintainers of those libraries will update them should MS pull the rug out from under us on something. For example, they did with a CU for SP2013 and required fields.