My Report won't open because it hates me. 1

[katiekat]

Ok, here's what happened. I spent days on a report, and it was very happy. It opened, it closed, all the great stuff a report can do to. This particular report was based on a query. It also had 2 subreports. These subreports were based on two different tables. Um, is that all the important stuff? yeah, i think so.<br>&nbsp;<br>So, I needed this report to show only a few reccords. So what I did was this. I went back and added some criteria to the underlying query. I then ran the report, and it was fine. I got the reccords that I wanted, it was beautiful. I closed the report, and the next time I tried to open it, the report refused. I don't get an error message, I get nothing. It just thinks for a minute, and then doesn't open. I tried taking the criteria off the query, I tried putting it back on. Nothing works. <br><br>I have a feeling there is a better way to filter a report, but I don't know what it is. If there is any way to fix the report, I would love to know. If not, if I screwed it that badly, I would like to know how to prevent that in the future. =) <br>Thank you!!!<br>Kate<br><br>Also, I am not a coder. I know some access SQL, but not enough to be truly useful. I am trying to learn tho, so don't get pissed. =)

 

[Stephenlyn]

Kate, reports don't hate people they just play tricks on them sometimes.<br><br>In the absence of anything else changing, have you got a date item in your report that is reporting for today when your records are from another day - the last time you ran the report.<br><br>Open your report in design view go to report properties click on the three... on the record source line and have a look at the report query.&nbsp;&nbsp;&nbsp;Click on your datasheet view to see if your query has returned any record.&nbsp;&nbsp;&nbsp;If it hasn't have another look at your query and change its criteria, if it has look at your report design.<br><br>hope this helps<br><br>Steve

 

[katiekat]

See, I think this one really hates me. =) <br><br>The thing is, I can't get into the report at all. The query is fine, it has no problems running, doing anything at all. The report will not open even a little bit. Design, print preview, nothing. I tried writing a macro, thinking maybe I could trick it into opening, but that didn't work either. There is nothing going on with dates, I don't think....all the dates I have are fixed, just &quot;this happened on this date&quot;, etc, and I am not reporting on them. It just won't open. At all. I don't get an error message, like, &quot;you don't have that query anymore, silly&quot; or anything else. It just thinks and then decides not to open it. It's weird. If I could get into the report, I am sure I could fix it, but it just won't open. <br>Thank you very much for your sugesstion!!&nbsp;&nbsp;

 

[peitzza]

i'm not that experienced at all but i had a problem (something) like you're having and repairing the database worked good for me... i'm sure you know how to do this but just in case... click tools&gt;database utilities&gt;compact and repair. <p>Peter Heaton<br><a href=mailto:heaton@characterlink.net>heaton@characterlink.net</a><br><a href=

http://castle.chaffee.net/~heaton>Take

it how ever you want</a><br>

 

[elizabeth]

If any underlying queries work, and you can't open it even in design mode, the object may be corrupted. If the compact doesn't fix it, try making a copy of it (select, cut and paste it in the report window). If the copy also doesn't work, you can also try importing it into a new database, then importing it back to your original database. Sometimes an import/export can repair a corrupted object or a corrupted entry in the System tables. And of course if that doesn't work you can go to your backup

 

[katiekat]

Thank You very much!! I have decided that it's dead, and there is no hope. I have tried everything, and I cannot ressurect the Report. Oh well. Next time I will have a backup.

 

[ProCatHerder]

Query based reports

I find that using a table makes for a much more stable report. Several times I've had bad behavior from reports based on queries, now I just go ahead and use a make-table query and use the table as a source for my reports.

ps: thanks for the chuckle re: your hateful reports - after hours of reviewing threads for solutions your's was a hoot!

 

[LogicalmanUS]

KatieKat,

Before you trash the remnants of the database you created, try one more thing.
Often a database or object can become corrupt, and a standard repair doesn't cut it. So..

Open a new, Blank database.
Open the old database to the Database window.

Drag and drop each object, from the old to the new, one at a time. This has the effect (sometimes) of simply copying objects over clean, without any metadata.

It's the last resort, but it has worked for me, plenty of times, in the past. So, what have you got to lose?

Logicalman.

 

[DonQuichote]

If my databases start getting drunk, it is time to decompile them. See

http://www.trigeminal.com/usenet/usenet004.asp?1033

For more info on this subject.

Best regards

 

[Stevehewitt]

I nearly gave a star for the title of the thread!

I had a similar problem once - those damn reports just keep getting moody. I managed to export it to another database, slapped linked tables and a copy of the query and it worked fine!

Good Luck

 

[FancyPrairie]

I'll give her a star for her title. It caught my interest.

 

[misterhux]

especially since she posted it three years ago

 

[SuicidED]

Lads & Ladies
Three years to reply to a post is not up to standard. Buck your ideas up.

Eddie

 

[Golom]

Actually, there were quite a few posts shortly after the original.

Why single out reports particularly? The OS, programming languages and databases generally have also exhibited a persistent antagonism toward me.