× 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.



Oh sure, new development. The only reason that I can think of for *not* using date data types is a mixed environment where the other (non-RPG IV) side doesn't understand them.

For example, I still have to (don't laugh) deal with the 36 environment. All of the new stuff that I do is in IV, but the II stuff still has to be maintained. That II code may, one day, have to access that new table with the date data type. But even then what I do is write an interface program in IV which is called by the II; the interface passes back what the II program needs (and can understand). So even a "mixed" environment excuse isn't a very good one.


        * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



rob@xxxxxxxxx wrote:
I understand that a little but I still have coworkers creating new, unrelated, tables with numbers as date fields.

Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.