|
| [mailto:midrange-l-admin@midrange.com]On Behalf Of jpcarr@tredegar.com <snip> | > In my era, our database design was dictated by its use, | | ah, you hit a nerve on that one. It is my belief that in | OUR day, we designed DB's for OUR use OUR program, OUR everything. | | Those days are over. It's the user's data base. They should have | direct access to it, and you cannot predict their ad hoc uses | from a myriad of interfaces. The Joins, Views should be designed | just as much for the End User's need as it is for OUR program's | needs. | | And SQL will be used by all those PC based interfaces. Can't agree more, John, with the above...!! Except that this was true in my shop back in '87. That's why, I suspect, We were able to develop custom systems with little to no payroll (at least I never saw much...;-). We were the custodians of the user's data, rather than the owners... They helped (or called themselves, anyway...;-) a lot on testing program outputs, because they knew the numbers and used them day-in and day-out. They also did all the on-going user training and were responsible for putting together user guides for the in-house systems (ie, there were none)... | | Last post I swear. | | Respectfully | John You and me, both, Bro...;-) Mebbe...!;-D
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.