On Wed, Dec 24, 2008 at 9:32 AM, justin <justin@emproshunts.com> wrote:
>
>
> Found the problem at last. it was what i thought early this morning, the
> database had some flaky data set to null. so modified the the tables in
> question set defaults to zero and updated all the records that has null to
> zero. hopefully that fixes the problem going forward.
>
> thanks to all for helping, pointing me in the right direction to figure out
> what is going on, as i was completely lost of what next to do.
Would it make sense to set that field to not null?
