Issue 77264

Summary: RPT: OOo should inform user when report designer is not available
Product: Base Reporter: drewjensen.inbox
Component: codeAssignee: lars.langhans
Status: CLOSED DUPLICATE QA Contact: issues@dba <issues>
Severity: Trivial    
Priority: P3 CC: issues
Version: recent-trunkKeywords: new_implementation, oooqa, usability
Target Milestone: OOo 2.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Example database none

Description drewjensen.inbox 2007-05-12 00:21:48 UTC
OOo is silent when when a user attempts to open Report Designer produced report
embedded in a base file on an OOo installation without the extension being
installed, or disabled.

Steps to reproduce:

Disable the Report Designer extension in your installation using Extension Manger.
Completely close OOo.
Download the attached Base file, ExerciseLog_RPT.
Open the file with OOo
Switch to the Reports section and double click on the report Designer_1.
Nothing happens!

This is a basic usability flaw - Let's say the suer had just received the file
from another person via email and was not aware of the Report Desginer
extension. ( it was not installed by his network admin person perhaps ) Most
likely the user believes the report should have run - trys again to run it,
fails. No message. He tries to run either of the other two - voila, no problem.

Right now the user believes the base file is somehow corrupt, which it is not
and if the report Designer_1 was the only thing in the file that he really cared
about anyway is at a loss for what to do next.

OOo should open a warning box telling the user why the report does not run, and
that installing Report Designer Extension will allow it to do so.
Comment 1 drewjensen.inbox 2007-05-12 00:22:27 UTC
Created attachment 45065 [details]
Example database
Comment 2 Frank Schönheit 2007-05-12 11:49:58 UTC
targeting to OOo 2.x
Comment 3 ocke.janssen 2007-05-14 07:36:22 UTC
Please take care for this one. Thanks.
Comment 4 lars.langhans 2007-05-31 13:22:46 UTC
duplicate

*** This issue has been marked as a duplicate of 77259 ***
Comment 5 marc.neumann 2007-06-14 10:14:19 UTC
close DUPLICATE