×
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.
It is not related to your problem (this time anyway) - others have
already pointed out the issue there.
However, I noticed in your code that you have a "naked" d data type in
your PI (i.e. one with no DATFMT specified). Unless you can
absolutely guarantee that nothing but an ISO date format will ever be
used by any program in your system this is a dangerous practice. A
naked d means use the default format - but the default can change from
program to program based on their H-specs. As a result, the prototype
that should protect you from passing an invalid date format into a
routine will fail to do its job if the PI/PR rely on defaults.
Personally I'd also specify the other data types in the PI/PRs - but
I'm just a cranky old man.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Jan 5, 2010, at 12:15 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
0047.00 D PI 1n
0048.00 dwItmNo 7 0
0049.00 dwLotNo 20
0049.01 dwUsrDate d
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.
midrange.com
