× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Al,

As others have mentioned, it is easy to change the way a numeric field
displays or prints. As I understand your process, Query #2 is adding
records to a file, so it is not necessary to "remove" the commas because
they actually do not exist in the file only on display. When you write
Query #3 to print a report, then you will want to format the number as
desired.

I suspect that if you run the command DSPFFD over the file from Query #1,
you will see that it has an edit code defined on the employee number which
would inhibit the commas on display.

Malcolm



From: "Al Gershen" <aldg1@charter.net>
Subject: Re: Query/400: How do you create a numeric field with specific
 characteristics?
To: mapics-l@midrange.com
Cc: "Gershen, Al" <aldg1@charter.net>
Date: Thu, 12 Sep 2002 12:38:29 -0400
Reply-To: mapics-l@midrange.com

Hi Lucus, Lisa and other Mapics ML members:

Thank you for your suggestions.  They have been helpful
and I'm getting closer to a solution to my Query/400
problems.

I have some additional questions:

Query # 1 produces a numeric field called EMPNO (Len 5,
Dec 0) that displays on F13 (Layout), as follows:

EMPLOYEE
  NUMBER
   99999

Query # 2 produces a numeric field called EMPNO (Len 5,
Dec 0) that displays on F13 (Layout), as follows:

EMPLOYEE
  NUMBER
  99,999

These fields are both "numeric" fields and have the same
Len and Dec settings.  Why does one have a comma separator
and the other doesn't?

How do I revise Query # 2 so that the comma separator is
removed?

Al Gershen
Grants Pass, OR
aldg1@charter.net




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.