OMG @sprenger. Thank you so much. I have been testing & searching for a solution to the same error message for an hour. It looks like perhaps this need to be fixed by the developer since I am not the only one.