|
Rob wrote:
Then why do you need SEU? Really. If you aren't supposed to be making
changes to the vendor dependent packaged software using WDSC you shouldn't be making changes using SEU. Well, they seem to forget that we have:1. 14 external vendors that we have to write programs for to interface with our vendor package. 2. We have a PC server based data warehouse application that we are continually writting interface programs for.
3. We have four websites that we have interface programs to.4. We have a PC based customer service application that we push data to from the vendor package. 5. We have an imaging system that we have to provide data to from the vendor package. 6. We have ACH applications where we have to accept data from external sources and massage the data before it can be processed by the vendor package.
7. etc., etc., etc...So, other than the reasons listed above (and many others that I can not recall at the moment), I guess we really don't need SEU and/or WDSc.
_________________________________________________________________On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
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
