×
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.
I concur, looking through the journals is an easy way to find this stuff
out.
Sequence . . . . . . : 1093737131
Code . . . . . . . . : R - Operation on specific record
Type . . . . . . . . : UB - Update, before-image
Object . . . . . . . : FSO
Library . . . . . : ERPLXF
Member . . . . . . : FSO
Type . . . . . . . : *QDDS
Date . . . . . . . . : 11/18/11
Time . . . . . . . . : 10:20:20
Flag . . . . . . . . : 1
Count/RRN . . . . . : 1049
Commit cycle ID . . : 0
Nested commit level : 0
Job . . . . . . . . : 349527/PATR/GDML6S3
User profile . . . . : PATR
Program . . . . . . : SFC500D2
The next entry is the "after image". So you can see exactly what fields
were changed.
Since we're a Mimix shop, journalling is required. But once the
department saw what journals can do they went hog wild. We're a bit
extreme - we keep our journals for 77 days. (2 month ends). Serious disk
usage? Yes, but that's our choice.
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.
midrange.com
