Print Page | Close Window

Logging Report Usage

Printed From: Crystal Reports Book
Category: General Information
Forum Name: Talk with the Author
Forum Discription: Ask Brian questions about his books and give him your comments. Like the book? Hate the book? Have suggestions? Let me know!
URL: http://www.crystalreportsbook.com/forum/forum_posts.asp?TID=9797
Printed Date: 04 May 2025 at 12:12am


Topic: Logging Report Usage
Posted By: JToine
Subject: Logging Report Usage
Date Posted: 23 Apr 2010 at 3:53am
We're back in the dark ages. We are supporting a version of Magic that uses ONLY Crystal 8.5.  We have about 750 reports that are served thru the app and another 60 or so that are scheduled.
 
We'd like to know what reports are being used.  We've tried creating a stored procedure in Oracle and calling it within the report header (we also tried the footer).  It logged the report but wrote an entry for every DETAIL record in the report.  That's not what we wanted.
 
We'd like a single entry that records the user, the report's name, and the date and time it was used.
 
With that information, we can better manage the growing number of reports.  If you know of a way to do this, please help!  Thanks.


Replies:
Posted By: hilfy
Date Posted: 23 Apr 2010 at 10:13am
You could try modifying the SQL for the report to call the stored procedure before it does the select statement.  In Crystal 8.5, you have the option to Show/Edit query.  In later versions you would have to convert this to a Command as you can't edit the query.  If you ever have to upgrade these reports to a newer version, you would have to rebuild from scratch in order to create the command as modified SQL from 8.5 and earlier doesn't upgrade well.
 
-Dell


-------------
Proviti, Data & Analytics Practice
http://www.protiviti.com/US-en/data-management-advanced-analytics - www.protiviti.com/US-en/data-management-advanced-analytics

Posted By: JToine
Date Posted: 23 Apr 2010 at 10:22am
Dell,
 
Thanks so much for replying.  Your suggestion is exactly what we attempted.  The problem isn't that it doesn't write.  It's that it writes, and writes, and writes for every record that displays in the detail section.
 
We only want a single line entry (User Name, Date, Report Name) to store in the database.  That's enough information to allow us to manage the report volume.
 
If you have any other suggestion, I'm open to it!  Thanks again.  I appreciate your offer.

Posted By: hilfy
Date Posted: 23 Apr 2010 at 10:32am
Is your date just a date or is it a date/time stamp?  Is there any way you can modify the stored procedure to prevent duplicates during a single run?
 
-Dell


-------------
Proviti, Data & Analytics Practice
http://www.protiviti.com/US-en/data-management-advanced-analytics - www.protiviti.com/US-en/data-management-advanced-analytics


Print Page | Close Window