Closed Raptorblaze closed 9 years ago
Apparently my original fix didn't resolve it reliably. Switched the proc to use safepick() and added a check for null return. Tested and the runtime error no longer occurs. Was symptomless, but better safe than sorry.
Apparently my original fix didn't resolve it reliably. Switched the proc to use safepick() and added a check for null return. Tested and the runtime error no longer occurs. Was symptomless, but better safe than sorry.