Why don't you modify your SQL WHERE clause to include WHERE B <> 0?

>I maintain a VFP5 app which has been in place for several years. Its purpose is to produce a table of summary data. It takes a couple of hours to complete and is usually run overnight.
>
>Occasionally a field in the final table will be populated with '*****' because there was a numeric overflow from invalid data. This is acceptable, and the app doesn't even blink when it happens.
>
>I've just made updates to several calculations within the app and am at the testing stage with a new version.
>
>All of a sudden the new version is throwing up an error (dialog box) saying 'Numeric Overflow data will be lost' and then waiting for user input. I can't figure out why this error is appearing now. Always before if there was an overflow, the app just stuffed asterisks in the field and got on with it. Because this app is run overnight, there would be nobody around to deal with it.
>
>Does anyone have experience with this? It appears to be occurring during an SQL Update statement doing a ( ( a/b ) * 1000000 ) calculation/replacement, but I have been unable to reproduce the error dealing directly with the data. (The cause of the overflow is a zero value in b).
>
>One other thing: the live app runs on one of our servers, where the error is occurring. I do development and interactive testing on my NT workstation, with no errors for the same data and code. The server VFP environment is unchanged and previous app versions do not show this error.
>
>Many thanks if you can help,
>
>Nanci