Hi all
Have been looking at all the responses to this and thought it might be useful
to point out another potential problem with values in numeric fields with a
decimal part. If you have a field MyField N(6,2) in theory it should have a
maximum value of 999.99. However VFP will happily store values like 9999.9, up
to 999999. IMO VFP should not allow this and it is a problem when accessing
the data using ODBC or OLEDB. The solution for us was to disallow values
greater than VAL("999.99"). The character part being constructed knowing the
field definition, in this case N(6,2)
Paul Newton
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Rafael
Copquin
Sent: 07 July 2017 18:22
To: [email protected]
Subject: numeric overflow
I wonder if there is a way to detect that a numeric field in a record is filled
with ******** as a result of a numeric overflow in a calculation
Please enlighten me
Rafael Copquin
---
Este correo electrónico ha sido comprobado en busca de virus por AVG.
http://www.avg.com
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/by2pr0201mb1797ee10eee8fefae8ba8eada1...@by2pr0201mb1797.namprd02.prod.outlook.com
** 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.
