Thanks sspuler for the workaround. I ran into the exact same problem everyone here is complaining about. It is clearly a program's bug that requires a manual patch. Note that you need to set the field to "0" and not just simply deleting it. Deletion won't work as it will repopulate the same faulty value back in place.
