|
IMO, wherever it is, the preferable method would be to avoid hard-coding everywhere "appropriate", and "when in doubt, take it out" of the program. There are data areas, special code files, etc. Many of these really should be programmer-driven. Even for the programmer, maintaining that code file is easier than making database changes. Thanks Alan
As an Amazon Associate we earn from qualifying purchases.
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
