At 12:43 2018-04-04, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
VFP9
I don't see why folks would use Numeric(X,0) where X > 4 instead of an Integer field. Can you tell me why? I'm guessing it's leftover legacy design?
There are a couple that I can think of:
1) Often, the numbers that I am dealing with are defined by number of digits. For example, my app has work order numbers of up to 999999. "N(6)" covers that nicely and even documents it.
2) The column width in a browse for a column defined as N(?) will be just right (assuming the caption is not too wide). If I declare the column as integer, it will be wider than necesssary.
Sincerely,
Gene Wirchenko
On 2018-04-05 13:19, Gene Wirchenko wrote:
At 12:43 2018-04-04, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
VFP9
I don't see why folks would use Numeric(X,0) where X > 4 instead of an Integer field. Can you tell me why? I'm guessing it's leftover legacy design?
There are a couple that I can think of:
- Often, the numbers that I am dealing with are defined by number
of digits. For example, my app has work order numbers of up to 999999. "N(6)" covers that nicely and even documents it.
- The column width in a browse for a column defined as N(?) will be
just right (assuming the caption is not too wide). If I declare the column as integer, it will be wider than necesssary.
Interesting...thanks, Gene!