… unless your have a good reason for it! Already a year ago I wrote my Validating Data series. And only a couple of weeks ago me and my colleague were investigating one of our solutions that had a performance issue and were faced with code that wasn’t quite SMART with…
Although you might be aware now that any code in the OnLookup trigger will leave you as a developer to handle everything yourself, you have made the choice to write your own lookup functionality. As mentioned in my previous post OnLookup & OnValidate #1, you not only need to program…
If you read Validating Data #3: Cascading VALIDATEs you know by now that a VALIDATE call comes with a price. So where possible the programmer should diminish the number of VALIDATE calls. Or “… to avoid the validate statement when populating records …”, as Marije Brummel puts it in one…
In my post Validating Data #2: Using VALIDATE I addressed the issue of how to validate code entered data by using the field method VALIDATE. In my notes, however, I mentioned that a VALIDATE call comes with a price. This is what this post is about and how to make the cost…