You might also want to contemplate the use of database triggers to ensure you capture all the information required.
A typical audit file is only ever going to be as useful as all of the programs that write / update it. As soon as someone performs a write or an update to the master file without including the audit file, then the audit trail is compromised.
We have found that installing database triggers will ensure you capture all database I/O's including SQL / DFU style updates, as the I/O is performed at the operating system level and not within the program.
Regards
Geoff
-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Gary Lewis
Sent: Friday, 27 January 2012 12:26 AM
To: 'System 21 Users'
Subject: Re: [SYSTEM21] System21 - Time from Pick Note to Despatch Note
Karim,
OEP55 is not especially "optimized" for inserts, rather, it's just that no one has bothered to create any sensible indexes over it. If you create the indexes necessary for your query they will perform fine. This is what I have done and use OEP55a extensively for reporting and audits.
Best regards
Gary.
-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Karim Khuweldi
Sent: 26 January 2012 13:04
To: system21@xxxxxxxxxxxx
Subject: [SYSTEM21] System21 - Time from Pick Note to Despatch Note
UPDATE TO JANUARY 2012 THREAD "System21 - Time from Pick Note to Despatch Note"
Ok here's how we've gone about it.
After some useful advice by Gary, we created two tables (in SQL Server), one for OE340 transactions (pick note prints) and another for OE125 transactions (confirmation of despatch).
These were populated from OEP55A: table OE340 with APRG55 = 'OE340' and ARCT55 = '2'; table OE125 with APRG55 = 'OE125' and ARCT55 = '2'.
A select query then joins these two tables to show the times (ADAT55 and ATIM55) for both transactions side by side and the amount of time between the two.
In theory, it should be possible to query the source table directly, without the need for the two tables above. However, OEP55A is a huge table and is optimised for inserts rather than reporting.
Regards,
Karim
________________________________
Karim Khuweldi
Sauflon Pharmaceuticals Ltd, 49-53 York Street, Twickenham, Middlesex TW1 3LP England
[cid:image0015985.gif]
________________________________
Contact Information
Tel +44(0) 20 8322 4277
Fax: +44(0) 845 051 8704
Email: KarimK@xxxxxxxxxxxxx
Web: www.sauflon.com <
http://www.sauflon.com>
________________________________
Disclaimer added by CodeTwo Exchange Rules 2010 www.codetwo.com<
http://www.codetwo.com>
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this e-mail in error please notify the originator of the message.
The views and opinions specified in this email may well be those of an individual and not truely reflect the opinion of Showerlux UK Ltd.
as a whole.
All possible care has been taken to ensure our network and email service remains virus free. We can not however accept liability for any virus transmitted to you from a Showerlux user. We urge you to scan any emails with your own virus software for your own peace of mind.
Showerlux UK Ltd is a company registered in England and Wales, registration number 1102862.
Registered office: Sibree Road, Coventry CV3 4FD.
VAT No: 273439150.
This message has been scanned by MailControl provided by www.cbs.cc/MailControl
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/system21.
midrange.com
