Hi Johnathan,
Not sure if this is related, or not. But when reviewing SQL warnings, and correcting them, that seemed to fix the problem. The warnings presented did not have any relation to the relevant field, but seemed to do the job.
Thanks for the help!