Joseph, have an ON ERROR routine which tests for the error number for "numeric overflow" - which is error number 39. If this is the error number then you can simply RETURN to let your program continue processing. Optionally, you could write the error out to a log file for later review and correction.
>Is there a way to trap for numeric data overflows? I'm SCATTERing and GATHERing between VFP tables, and I'm also uploading to SQL Server. A numeric overflow prevents my programs from working. How can I look for those kinds of problems and set them aside so my programs will continue working?
In the End, we will remember not the words of our enemies, but the silence of our friends - Martin Luther King, Jr.
