Nope that isn't it. I updated the view and still go the same error. True the back end table had been modified, but the view was updated along with that modification. This error occurs during run time and not everytime either.