|
Actually I still stick with Praveen, unless there is a "NEED" for all fields. Case in point. We had a nifty sql used to pull data from BPCS files. At the time it was supporting multiple flavors of bpcs so the file layouts changed. We picked one flavor to compile from, set up the external DS based on that version's file and used the SELECT *... Other than a minor warning message because of some ignored fields at the end - no problem. However we put on a new version of OS and that minor warning message was escalated to a "hell hath no fury..." message. That was numerous versions ago and probably even JHHL would be affected. So we still use the external DS. But now we pick and choose fields. Granted, more typing for the coder. However it's supposed to be faster because less data is moved around, etc. I suppose then if you start doing weird stuff like implementing column level security, etc then you'll have less trouble if you just don't ask for what you don't need. Rob Berendt
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.