×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The thing about looking at the journal receivers itself instead of data
gleaned from them is that the journal receivers pretty much defy tampering
with them. You delete a journal receiver and it logs it to another
receiver. With the usual who, what, when, where.
Use a tool and whose to say the tool doesn't have logic to omit any UPDDTA
against the direct deposit file from programmerb?
Would your tool display the "journal turned off" and "journal turned on"
messages that programmerb did to hide changes made?
Don't get me wrong - tools can really pretty up something to take to
management. But learn the bits and bytes of journalling.
You can manage your receivers and save them off to tape and purge them
when necessary. Actually we keep them for 77 days to get two full month
ends. Huge amounts of data but it's used - a lot.
Would typical audit logs be as acceptable in a true audit as receivers
are? I doubt it. For instance, my item master maintenance report prints
off add, changes and deletions. Or records them in a file. Big whoopie.
Bet it doesn't catch other updates against the file.
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.