@ jm, thanks for the tip. Yup it's a culture thing. Windows 10 allows a user to customize the way numbers are shown and in this specific case, the user chose " , " as the decimal separator. The moment I changed that setting, the exception went away.