I think it depends on shop. For example you may be externalizing I/O and
by table may make sense for you. Then again, it may not. Because if
you're externalizing I/O the name of the 'table' shouldn't matter.
Organizing by application may be applicable. For example: A/P, A/R, etc.
Or even by software vendor.
We have very few custom service programs. I think they are all in our
ROUTINES library. All prototypes for the various procedures in those
service programs are in QPROTOSRC.
Rob Berendt
This mailing list archive is Copyright 1997-2026 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
