I simply highlighted one example where/how the error could occur. The replace command was used as an example only. If I could test the field I wouldn't need to look for it, woulf I
SdB On Mon, Sep 29, 2008 at 7:52 PM, Allen <[EMAIL PROTECTED]> wrote: > I would have expected that testing for a number bigger than the field can > hold is a good start. Fsize gets the field size and type the type of field. > > Al > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On > Behalf Of Sytze de Boer > Sent: 29 September 2008 06:04 > To: [EMAIL PROTECTED] > Subject: Numeric overflow > > Hi Folk > > In my error routine, if the system bombs out on error 39, I pop up a > message > to tell the end-user about the error etc, BUT THEN the system carries on. > > I know there's a zillion circumstances why error 39 can come about, but > what > I really would like to know is what FIELD or memory variable is involved > that is in the state of **************** (numeric overflow) > > e.g. > Let's say I have a table with a field called amount N(5) > > REPLACE AMOUNT WITH 1000000*100000, SUMTHING else with 7890 I get error 39 > How can I tell programatically that it is AMOUNT which is now ****** > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
