[Solved]Error opening large documents created in Word 2010 in Word 2013

When you open a large
2010 word document in word 2013, it can yield an error of type:
We're sorry. We can't open XXXXX.docx because we found a problem with its contents.
Details:
Operation aborted: max-element-depth constraint violated.
Location: Part: /word/webSettings.xml, Line: YYY, Column: ZZZZ
To fix this error, you have to rename the .docx to a zip file, delete the file Websettings.xml and then rename back to a docx.

To fix this error, you have to rename the .docx to a zip file, delete the file Websettings.xml and then rename back to a docx.
I've been having the same error and this solution worked for me. It seems to be linked to documents built using Mendeley's reference plugin for Word. This issue is mentioned on their support site (here)
and that may be why the issue comes up with dissertations &c. The fix is easy and it works, but I would suggest you do the fix using a
copy of your document. That way if anything goes wrong you still have the original.

Similar Messages

When I try to open a document created in Pages, I get an error message saying "[Document Name" can't be opened." I don't want to lose hours of work; has anyone else encountered this?

When I try to open a document created in Pages, I get an error message saying "[Document Name" can't be opened." I don't want to lose hours of work; has anyone else encountered this?

A few general trouble shooting tips that may apply here:
1. If you used Software Update to do the OS update(s) to reach 10.6.7, go to http://support.apple.com/downloads/ and download and apply the Mac OS v10.6.7 Combo Updater. The Combo Updater contains some fixes that were not included in the incremental updaters used by Software Update.
1a. Check that you have the current version of Pages (and of the other iWork applications) installed. All three applications' current version numbers end in .0.5
2. A common cause of malfunctioning applications is a corrupted preferences file (.plist file). Your Pages '09's plist is at yourname > Library > Preferences > com.apple.iWork.pages.plist
Quit Pages, locate the file and Drag it to the Desktop (or to the Trash).
Restart Pages and attempt to open one of the files.
If all is well, Trash the plist file and empty the Trash.
If there's no change, AND you've made changes to the Preferences that you wish to keep, drag the file back to its previous location, replacing any new one that has been created.
Regards,
Barry

"There was an error opening this document" Adobe PostScript Driver creates corrupt PDF's.

Hello,
Just looking for a point in the right direction or some answers to a problem that has been plaguing a few of our users.
We use Adobe reader X and Adobe Post Script driver as a means to print a document as a PDF.
However, a few of our users are experiencing the problem where as the every so often a PDF created comes up with the "There was an error opening this document. The file is damaged and could not be repaired." Message. these documents always vary in size but average around 20 - 30 kb, These seem to be complete anomolies and are corrupted from the off. The only solution we have found for this is a complete rebuild. But we have no idea what is causing this, as we are using the latest version of Adobe Reader. Also, a document that will print corrupted on one go, will print fine on the next.
Thanks.

Hi Lori,
Thanks for your reply currently all users access these PDF's through the standalone reader and users on the most up to date version of Adobe Reader X are not using protected mode as we have had it turned off for a while to fix other problems.
Thanks

There was an error opening this document. Access denied.

Greetings,
When I did my taxes last year (March 2012), I downloaded some pdf files from the IRS. Form 1040 was a writable file and I filled it out as needed. This file was saved on a Vista machine running XP. A few months ago, I upgraded that pc to be Windows 7 SP1.
Today I'm getting ready to do my taxes for this year. When I double click on last year's Form1040.pdf, I get the following error message:
There was an error opening this document. Access denied.
Interestingly, I can open other pdf files, like the Form 1040 Instructions. I do not think that I password protected my Form1040.pdf. The reason that I think it isn't password protected is because I'm not being prompted to enter a password.
I copied the file to an old spare XP machine (XP Home, version 2002, SP3) that I have and it opened fine. It did not prompt for a password. I printed copies of last year's forms from that XP machine, so this isn't an emergency for me, but it is mildly annoying that I can't figure out what's wrong.
I have Adobe Reader XI version 11.0.2 installed on both machines (the Windows 7 machine and the old XP machine).
To summarize, it was created on Vista, I can't open it with Windows 7, but I can open it with XP.
Normally I would consider uploading the file in question, but in this case, I hope you'll agree that might be a bad idea!
Advice on how to get this to work on Windows 7 would be appreciated.

Pat Willener: Thanks! That solved the problem.
For anyone else having this problem, here's a detailed list of how I used Pat's advice to solve my problem:
1. Right click on the problematic file
2. Select Properties
3. Select the Security tab
4. Press continue
5. In the "Permissions for MyFile.pdf" dialog, press "Add".
6. In the "Select Users or Groups" dialog, press "Advanced".
7. The next dialog that pops up is also named "Select Users or Groups". Press "Find Now".
8. Scroll down the list of search results until you find your username.
9. Double click on your username.
10. Press ok in the "Select Users or Groups" dialog.
11. Press ok in the "Permissions for MyFile.pdf" dialog
12. Press ok in the Properties dialog.
done.

Sorry, we couldn't open...Error opening office documents from SharePoint 2013 in the desktop applications

Sorry, we couldn't open...Error opening office documents from SharePoint 2013 in the desktop applications
One of our Managers encounters the error 'A problem occurred while accessing the Office document cache. Do you want to repair this problem?'
Then When he says yes it give a warning that the cache will be backed up and replaced
Then it says 'A new office document Cache has been created...'
Then it loads this cache with an error
Then After all that the next time he tries to open the document it says is encountered "Sorry, we couldn't open 'URL."
We have Reinstalled office 2013 on the users PC repaired the cache numerous times
Followed -  http://office.microsoft.com/en-gb/word-help/manually-rename-the-office-document-cache-HA101848838.aspx
Updated Lync to 2013 leaving Access as the only office 2010 application (required for legacy systems access)
Repair installed office 2010 and office 2013 again
The SharePoint site has been added to the trusted sites list and the set up assistant run from office 365
And the issue remains the Same all other users including some who also have Access 2010 for legacy systems access have no Issues OS is windows 7 32 Bit browser is IE 9
Office 365 said
Reply by Rachel Zhang MSFT Support
Hi Alex,
From your description, I notice that the issue is related to Office client. We would like to help you, but I’m sorry that our forum does not focus on this scenario and has limited resources regarding it. However, we have a dedicated support forum where
the support engineers will help you with the issues about Office client:
Microsoft Office Community:
http://answers.microsoft.com/en-us/office/forum/office_2013_release?tm=1365567547805
Feel free to sign in to the Office community and click Participate->Ask a Question to post the question with the relevant information.
Microsoft Office Community:
Feel free to sign in to the Office community and click to post the question with the relevant information.
Office team said
Hello Alex,
Thank you for posting your query in Microsoft Office Community.

Check if other excel works fine
Do you have any script\macro in excel file
Check if all application pool on all servers are running
both office and IE should be same build (64 or 32 bit)
what is the error message in ULS log and Event viewer
If this helped you resolve your issue, please mark it Answered

SSRS PDF Export. There was an error opening this document. This file is damaged and could not be repaired

Hello,
I just experienced this problem, and was able to successfully mitigate. I wanted to share my experience and Solution.
The problem started with the following error after succesfully exporting a PDF Document. "There was an error opening this document. This file is damaged and could not be repaired."
This is only applicable if you can still export and open SSRS Reports to other formats. Go to the Log files of the SQL Instance. In my particular case I used the Default MSSQL instance: C:\ Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
Services\LogFiles
The Folder will begin with MSRS (SRS is for SQL Reporting Services)
Sort the files by date modified and check for the most recent log file: ex. SQLDmpr0000.log The 0000 will be the incremental amount of errors you have experienced in SRS. Check for the following error:
"System.DllNotFoundException: Unable to load DLL 'T2Embed': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
Below is a sample from the log.
reportrendering!ReportServer_0-1!1b78!02/07/2012-11:56:03:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: , Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException:
An error occurred during rendering of the report. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.DllNotFoundException: Unable to load DLL 'T2Embed': Access
is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.TTGetEmbeddingType(Win32DCSafeHandle hdc, UInt32& status)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.CheckEmbeddingRights(Win32DCSafeHandle hdc)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.ProcessFontForFontEmbedding(PDFFont pdfFont, Dictionary`2 embeddedFonts)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.EndReport()
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream
createAndRegisterStream)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderFromOdpSnapshot(IRenderingExtension newRenderer, String streamName, ProcessingContext
pc, RenderingContext rc)
   --- End of inner exception stack trace ---;
If you notice the error states that T2Embed.dll access is denied. In my case this due to a hotfix installed by Microsoft:
MS11-087: Vulnerability in Windows kernel-mode drivers could allow remote code execution: December 13, 2011
Be advised, in order to fix your problem and render pdf's, a vulnerability shall be created.
To fix this issue and allow the export to PDF work correctly, you must give the system Read/Execute Permissions, and Built-in\Administrators Full Control.
Go to Windows\System32 and find the T2Embed.dll Go to Security and modify the permissions as listed above. Do the same to the T2Embed.dll in the SysWow64 folder.
Restart Reporting Services and you will be able to export to PDF.
Best Wishes!
Mariano
www.lucontech.com

I'm not convinced this is the exact cause of the issue. I will check my log files to see if I find anything like what you described. However, I get this error when a particular user tries to do a "print preview" from a custom button. The
code builds a ReportViewer object, sets the ReportPath, etc.
The reason I'm not convinced is because we have a separate reports page that has the report viewer embedded into it. If the user generates the report that way and exports to PDF, Word, etc...the user can generate the file and be on their way. As
soon as the user clicks our "Print" button on the page without the ReportViewer embedded, the above mentioned error occurs.
UPDATE: Perhaps we have a different problem since my issue is from a custom button. I found the solution
here and confirmed the solution with the customer. It had to do with the code using Response.Flush() instead of Response.End().
One thing I noticed before I implemented the change: When you would close the PDF, it would ask you to save changes to the PDF. After implementing Response.End() instead, that prompt went away. No doubt it has to do with the differences between
how Response.Flush() and Response.End() handle the stream returned.
Anyway, posting in case someone has the same issue.

Error with Adobe Acrobat X "error opening the document. The file is damaged and could not recover"

Good morning,
I have a problem when generating PDF files with Adobe Acrobat X.
When I give print a Word document 2003 ... 2007 ... 2010 ... and select a network drive to save the PDF file, I get the following error "error opening the document. Thefile is damaged and not could recover."
The file is saved on your drive well ... but I always get this error.
Any ideas???
Thank you.

First of all thanks for responding.
The installed version of Adobe's Adobe OS X and Windows XP machines is thelatest patch level.
The local system .... works well ... Open Office 2010 ... create a new Word document and save it locally ... and all good.
The problem is though that same machine ... it enters network (not Windows network. OES2 is a network with Novell network client) ... and to open and create a new document to WORD .... when printing the PDF printer ... select a network drive... and when the document is saved well ... but it shows the error.
I have an amount of hours lost with this ... I hope you can help me find a solution.
Thank you very much.

With Reader XI There was an error opening this document. Access denied

Hi there, It looks like I have a simular problem. I also get the error "There was an error opening this document. Access denied." This when I tried to open the file by clicling on the file. When I try to open the file from out Adobe reader it gives me the error "You don't have permission to open the file" I use Adobe XI. My OS is W8.1 By clearing protected mode doesn't help. This is what I found sofar: Only the PDF files in the documents and subfolders are giving me this error. PDF files in other folders are fine. When I copy PDF files from the documents folder to Desktop they open without any problem. First I thought I might be a permission problem with the Documents folder, but I have full access. Other files in the Documents folder like Word and Excel files open fine with MS Office. My laptop has WinXP and is shared with my PC when I open PDF files on my laptop by using the network share they open without problems. So it looks like only the PDF files in my Documents folder. I'm not sure but before upgrading to W8.1 from W8.0 I can't remember if I had this problem, but I think I did not have it. To make it even more interested is that I have also Adobe Acrobat Writer on my PC what I use for my buisiness. When I open the PDF files with this program they open without any problem. Therefore I believe it is not a permission problem, I still believe it is a problem with Reader XI, but than only after upgrading to W8.1, but as I already mentioned I'm not sure for 100% only that sofar I know it never happened under W8. Has anyone out there simular problems? And hopefully with a fix.

This is what I did sofar: Deleted reader XI and reinstalled same problem.
Because I think the problem is with reader XI I deleted again XI and installed reader X.
With this version I can open PDF files located in the documents folder without any problem.
For now I keep using version X until they fixed version XI
This proves that reader XI will not work under W8.1 when opening PDF files in de documents folder.
Bennie

Another "there was an error opening this document. this file cannot be found"-question

Hello people, as the title suggests, i have another question regarding the "there was an error opening this document. this file cannot be found" error. I have searched on Google and on these forums but i havent found an answer to my particular case (sorry if i overlooked it).
I work at a supportdesk for a company that uses Windows XP with Adobe Reader version 8.1.3.
Users are getting this error when they access a PDF file placed on a (mapped) networkdrive. Contrary to some other cases i have found on this forum, spaces are handled without a problem. But a comma in the name of one of the folders that contain the PDF file are what causes this error.
i.e.:
Opening the following path results in the error:
L:\X, Y & Z\adobe.pdf
Removing the comma so the path becomes:
L:\X Y & Z\adobe.pdf
works just fine.
So far our workaround has always been to simply remove the comma and move on, but I've been wondering why this comma is such a problem for Adobe Reader. As far as i know Adobe Reader is the only program we use that has this issue, M$ Word works just fine with it to name an example.
To sum my questions up:
- Why is comma (,) a problem for Adobe Reader?
- Have i missed any patches/new versions where this issue has been addressed?
- What is Adobe's stance on this, and are there any plans to "fix" this?

Ok, nevermind, we just found the problem
It's not Adobe Reader that is causing this, but another program the company uses to manage/distribute/authorise programs that users are allowed to access (Scense). I had never even considered another problem could have caused this for Reader.

There was an error opening this document. This file cannot be found

An automation script on one of our QA environments kept tripping on the error: "There was an error opening this document. This file cannot be found". The same script ran fine against our Production servers (hint, which were "whitelisted").
It took a little time to resolve/trace what was happening (but with the aid of ProcessMonitor and tracing all "pdf"-related file activity...)
The problem lies squarely between McAfee (75%), Adobe (20%) and Microsoft (5%):
NORMAL WORKFLOW. IE (Internet Explorer) when popping a PDF document, has to (1) write the document to the IE cache, then (2) launching and "handing off" the document reference to the Adobe viewer (which might then be able to open the document, et al) -- assuming largely a "synchronous" workflow.
BUT "WAIT", HOLD THE HORSES -- McAfee takes ownership and decides infact "wait for us" (during the workflow), it wants to first perform a virus scan on the document (ahead of writing the document to cache) involving potentially large latency (delay) before making the document available to the system. However, instead of "fessing up"-that their scan may be taking too long, McAfee appears to have taken their work "off-line" in violation of the sychronous interface above. I'm guessing the developers at McAfee might have been trying to hide any extra processing overhead being incurred by assuming they could somehow convert this to an "asychronous" event. (This may also have more reach than just PDF's.)
Unfortunately, the browser's "PDF OPEN"-dialog box pops allowing Adobe to launch-and-open the "as-yet-not-virus-scanned-and-thus-not-yet-cached"-document. Thus clicking the OPEN-button will cause the related "...FILE NOT FOUND"-error to be seen (because the file is still in McAfee "limbo").
Note: If you close the ADOBE reader (but don't yet close the popup-OPEN-dialog) you can click OPEN a second time and it will probably now open the document - which McAfee finally finished scanning!
You can observe all these interactions with ProcessMonitor, and use the monitored file states to adjust the timings of events to reproduce both the failure and non-failure scenarios.
- Best Regards, Ziggy
ps. My assessed distribution of "ownership" of the problem is because ALL these parties should be aggressively resolving this for the customer-base!

What, exactly, were you trying to do when you got it, and how?

"There was an error opening this document. The filename, directory name, or volume label syntax is i

"There was an error opening this document. The filename, directory name, or volume label syntax is incorrect."
I tried different versions, no avail.
I think it has to do with the password somehow, but I do not know. I can copy the files from the web folder to my desktop and they open fine (after entering the password AGAIN), but I can not open them directly form the web folder - it does not ask for the password again, just pops up the error.
Adobe's support really upset me (insert explicative here) by keeping me on the phone for 20 min, collecting all sorts of information about me (not the problem) with some lady who barely spoke English, just to tell me to go to the website. No surprise they need to charge for tech support, customer service is doing everything but "service". I hate companies that do this. I am thinking of using another PDF reader, I have heard good things about them. Check
http://en.wikipedia.org/wiki/List_of_PDF_software
Has anyone ever been able to find a fix? I can not find anything on this site.

Howdy, Moritz!
Thanks for the suggestion, but this is not an issue of filename and language conflicts, at least in my environment. I highly doubt that's the root cause of this issue.
The PDF files in my tests have all had very simple names, such as 123.pdf and test.pdf, as well as more complicated names with spaces in them. Nothing about the files contains anything outside of the English language, including the content and filenames.
From everything I've been able to determine, this is a WebDAV-related security issue that affects programs like Acrobat Reader. I know for a fact that MS's KB892211 WebDAV patch doesn't create the issue, however MS's update to that 892211 patch DOES create the issue. As I've outlined earlier in this thread, my extensive testing has proven this more than once.
At this point, I haven't been able to accurately uninstall the update to 892211 after the update has been installed. And, as far as I can tell, the update to 892211 comes down from MS as a Office and/or Windows Update component. So, everyone has it, the uninstaller doesn't work, and there's no documentation detailing what registry entries are being changed when the update to 892211 is installed.
My ultimate goal is to bring a test machine to the point just before the update to 892211 goes on, fire up the Registry, Process, and File monitors on my test box, and install the 892211 update. This should give me an accurate picture of what I need to restore in order to rid the machine of the update to 892211.
Until Microsoft officially fixes the issue, I am not totally sure how this will be resolved. I've ceased my work on the issue for now since copying the PDF file from the WebDAV share to the user's desktop gets the user what they wanted in the first place - the ability to open the PDF file!
Maybe, once some other projects slow down a bit, I might get back to creating a solution, but it's going to be a "hack" no matter which way you slice it. I'd much rather MS spend their time creating the solution. If I have to do it, my fee to MS will be quite HIGH! :*)
George B.

There was an error opening this document. The file is damaged and could not be repaired.

Good Day all
When busy doing internet banking on www.absa.co.za and I try to print a confirmation, I get the following error message: "C:\Documents and Settings\%user profile%\Local Settings\Temporary Internet Files\Content.IE5\%folder name%\%file name%.pdf
Could not open file.
File not found."
I've managed to locate the actual file that it's looking for, but when I try and open the file using either Adobe or Foxit Reader, I get the following error message: "There was an error opening this document. The file is damaged and could not be repaired."
I've un-installed Adobe and installed version 9.1 for this particular user. This happened a while ago and then an un-installation and re-installation of Adobe solved the issue. This time, unfortunately, it didn't. I then un-installed Adobe and tried again, UNSUCCESSFULLY. So I loaded Foxit Reader, also without any success.
If there's anyone out there who could possibly help, please do so... It's extremely urgent.
Please find the errors attached as well.
Regards,
ME

I contacted the company and they asked me to try using another browser, which I did... and using FireFox worked
thanks for the help ʇɐb ɹəuəllıʍ
cheers!

There was an error opening this document. This file is already open or in use by another application

I cannot open any PDF documents. I receive one of two error messages:
"There was an error opening this document. This file is already open or in use by another application."
"This file is in use. Enter a new name or close the file that's open in another program."
I do not know how to open the document in another program, so I am perplexed how it could be open in another program.
I tried Repair the Adobe Installation from within Adobe Reader and from the Control Panel (Control Panel\Programs\Programs and Features\Uninstall or change a program) using the Change option. I'm assuming they are the same process, although I'm not sure. Neither method worked. I rebooted after each.
I'm at work at a huge federal agency, so we're of course on a network. It takes several days to receive agency IT help, which is why I'm asking here. I can open Word and text documents. Nothing else seems to be amiss on the 'ol pc.
Adobe Reader 11.0.05
Windows 7
As you can tell, I have only limited knowledge of the possible issues.
Thanks!

Shared network drive.
I was not able to open the PDF documents via Notepad.
Interestingly, and perhaps supportive of your hypothesis, I subsequently had problems with Outlook wherein I could not save or close an email I was writing because "you do not have permission." I rebooted my computer and now Outlook works fine (and it save my email, thank goodness), and I can open PDF documents.
Hopefully it will stay this way. If not, I'll be back!
Thank you very much for offering to help.
All the Best,
Mark

Pro 9 Users Receive "There was an error opening this document. The file is damaged and could not be repaired."

Users with Adobe Acrobat 9 Pro (Windows XP) are not able to open PDFs created on the server. They receive the error message:
“There was an error opening this document. The file is damaged and could not be repaired.”
Even if the users save to disk and try to re-open, the error still occurs.
This error did not surface in our QA testing because we were testing with Adobe Acrobat Reader 8. What can the difference be? Is there additional information that I can look for in order to troubleshoot this?
Thank you for looking at my post. Please provide guidance in trying to resolve this issue.
Elsa

So, I'm not sure how much this will help but if you save the pdf AHW_Test_05112009xx.pdf and open it in a text editor, and go all the way down to the bottom where the %%EOF marker is, it looks as if the html page is getting appended to the end of the pdf. I recieved the "This file was damaged..." error in Adobe 7.1.0 when trying to open it but if you remove the html at the end, it opens up just fine.
It appears that whatever's appending the html to the end is causing the issue.
Below is what the file looks like near the end after the EOF:
startxref
400771
%%EOF
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head><title>
Gartner for IT Executives
</title>

Exporting PDF files from SSRS 2012 - "There was an error opening this document. The file is damaged and could not be repaired"

Good day
I have the situation where we are exporting PDF files from reporting services in our website.
When dividing the data into sections, the report exports perfectly, but when exporting the entire set and trying to open the file, we get the following error in Adobe Reader:
"There was an error opening this document. The file is damaged and could not be repaired"
We tried to repair the file, no luck. We tried to use different PDF readers, no luck
We then checked the file sizes. When exporting the subsections, each section exports a file of about 2mb.
When exporting the entire set, the file is about 1.3mb.
Adding all the sections together gives me a rough estimate of 40mb.
Exporting to TIFF works beautifully and returns a file of 41.5mb. Word and Excel formats also work well, only issue there is the page numbering and formatting.
The problem we have is the clients are adamant about having it in PDF format.
Any advice please?

This was one of the temporary suggestions I gave the client...
Unfortunately they do not like this as the page numbering and formatting in Word does not appear right. We are talking about over 1300 pages. I can't expect them to change the formatting with each export. Additionally, the data is
constantly changing and each client has their own data. The clients export the reports randomly. I therefore can't post the reports back onto the server.
Thanks for the speedy response though

[Solved]Error opening large documents created in Word 2010 in Word 2013

Similar Messages

Maybe you are looking for