J
James Palmer
Guest
I agree that this is ok once the locking issues are resolved, but you don't want to just turn it on in Prod when you know you have locking issues. You don't want the user to be presented with a big error, particularly if you have transaction scoping issues that mean the error from not having a lock on a record mean you undo all the work for today. So turn it on in Dev and Test, fix the errors, then turn it on in Prod.
Continue reading...
Continue reading...