Issue 78153 - Base 2.2 Report will not open
Summary: Base 2.2 Report will not open
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.2.1 RC1
Hardware: All All
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords: needhelp, needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2007-06-06 17:43 UTC by johnooo
Modified: 2008-06-17 16:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description johnooo 2007-06-06 17:43:22 UTC
Using Base 2.2.9134, to compile report, then report will not open,also report 
cannot be deleted.
Comment 1 Mechtilde 2007-06-20 20:59:45 UTC
Can you give a step-by-step description?

what do you mean with"compile a report"?
Comment 2 johnooo 2007-06-20 22:00:53 UTC
Using windows xp, by compiling report I mean selecting the fields required and 
construcing the report using wizard.
After compiling report,  and naming it ,opening it,I then decided to give it a 
differant name, after this the report would not open and will not delete.

I have recompiled the report and all is fine except the old report box hanging 
in the report area.

This problem has also been reported on the Forum by SDCSLLC on the 14th June.

Comment 3 marc.neumann 2007-06-21 08:26:02 UTC
Hi,

I can't reproduce this with a 2.2.1.

Can you attach the bugdoc database to this issue?

Thanks and bye Marc
Comment 4 johnooo 2007-06-21 08:43:19 UTC
I cant give you the database in question, however i have tried to replicate 
this in 2.2.1 and I can't do it.Perhaps it is worth contacting the other person 
who raised the issue.
Comment 5 christoph.lukasiak 2007-09-03 14:17:51 UTC
clu->johnooo: a bug must be reproducable (else it is not fixable)

clu->all: if anybody can confirm that behavior, please add a step by step
description
Comment 6 johnooo 2007-09-03 16:25:56 UTC
I think this occurs when a forward slash ie /is usedin the report title. for 
further information see Base Forum report 28 Aug by Elektrodwarf and the reply 
by Drew Jenson.
Comment 7 Mechtilde 2008-01-07 22:07:24 UTC
@ johnooo

Can you give a link to the post in the forum?

Otherwise the issue can be closed as invalid
Comment 8 drewjensen.inbox 2008-06-01 06:26:45 UTC
Given the length of time and that the referenced posts at the forum did have to
do with a known issue, invalid character in name, that has been fixed in the
package for the last few releases I am going to close this as INVALID
Comment 9 christoph.lukasiak 2008-06-17 16:59:17 UTC
=> close

do not hesitate to reopen this issue if still occurs in current version

thx