|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] jt, It's common practice to temporarily grab *ALLOBJ. For example; I have two disparate systems. Accounting by Software Plus, ERP by BPCS. When I feed from one to another a custom program is written that adopts *ALLOBJ authority to transfer from one to another. Granted I could adopt a profile that does not have *ALLOBJ, yet has access to both sets of data (and often do use this method). Now I am sure there are valid reasons for a single vendor solution to temporarily need this authority. As much as I would like to search it out like a hawk, (after that one bad experience), I cannot. I suspect a lot of it has to do with copy protection schemes. The vendor needs to check out stuff normally limited to God like authority to make sure that you aren't copying their software to another machine. In a perfect world they wouldn't need to worry about copy protection. Yet, in a perfect world we wouldn't need to worry about security. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
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.