Failed to save document

[steenbreker]

In march 2003 GBuchman asked the same question, but didn't get any reply. I've the same problem: After 5 hours of editting a report with 16 subreports, when i want to save my work, it tells me "Failed to save document". I cannot save under another name, another location, or on CE. I've tried reducing the nr of subreports and putting them in other sections, nothing works, just this dumb "Failed to save Document" without any further explanantion. Does anyone have a clue ? In the meantime i'll keep my PC and CR up and running for the next few days, hoping to find a solution.

 

[synapsevampire]

Unfortunately it sounds like a corrupted report, hopefully you have a backup.

Every significant change in a report results in my renaming it during development for this very reason, you aren't alone in this experience.

You can try eliminating subreports, turning off the File->Save data with report, and changing the connectivity from whatever you're currently using in whatever version of Crystal you're using.

BTW, posting the version of the software, connectivity and database being used is always helpful.

-k

 

[Ngolem]

I will add one other thing to SV's comment.

I ALWAYS save BEFORE trying out something that I have never tried before.

I should say that this has come from brutal trial and error. I used to never save for hours and end up having to redo a report all over again when it hung or my computer crashed. (My only saving grace was that it was usually better the second time around )

Never do a major change and try it out before saving... the odds are that is when your computer hangs and all is lost Save it first...then try it out...if it hangs or crashes...reboot and try to figure the cause.

Jim Broadbent

The quality of the answer is directly proportional to the quality of the problem statement!

 

[hilfy]

To solve your immediate problem, have you tried creating another report then copying the subreports from the original and pasting them into the new one? If you save after every "copy", you should be able to get a clean version of the report.

-D

 

[steenbreker]

Thanks hilfy, the thought had already crossed my mind once, but i only tried it after your reply. It was still a lot of work, but starting all over again would surely have cost more time. I've had the error message "Failed to save document" a number of times before, after a small change, so i didn't bother then, just started over. Anyway, i'm still curious to know what causes it, so i might be able to prevent it next time.

-S

 

[kmcmanus]

I am also getting the message on a version 9 report (service pack 2 applied). The report was running very slow with no subreports and the only thing that I have done is checked the database links and verified the database.

Now the message "Failed to save document" comes up. Once it came up with a message bout not being able to save query object, but now I cannot get that to reappear. The only hint I get in mine is the Database Warning message states "More than one datasource or a stored procedure has been used in the report. Please make sure that no SQL expression has been added and so server-side group-by is performed."