I have this problem. I'm working with .cdr file which is large in size(93Mb). But today suddenly when I run a custom Microsoft Visual C++ 6.0 on a computer running Microsoft Windows XP, I receive the following error message:
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
Glitches excluded relating to the size of the file, as in previous similar situation was taken the last of the normally open cdr files. Working with it was continued and it worked perfectly. Of RAM enough (behavior Corel tested on 3 computers, one with 2 GB of RAM). VIRTUAL memory and SPACE on the screw enough...
To fix Gluck did the following:
1. Put Service Pack (SP1) for Corel Draw 12 , the situation has not changed...
2. Updated dll for mfc 7.1, the situation has not changed...
3. Replaced the files Msvcrt.dll and Msvcirt.dll from 7 to 6. Replacing one of these files (don't remember exactly what) does not manifest itself, and when replacing other Windows XP it does not boot...
Full uninstall of software, reboot of system and reinstall of software.... does that fix the problem?

If that doesnt fix this, then a clean install of the system would be best to correct for corruption with the OS, and then reinstall Corel Draw 12 and be back up and running.

*Be sure to backup your data to an external drive FIRST before a reinstall of OS if thats the route you go with this.Try to download the hotfix on the Microsoft website and fix this error. Look in more detail here.
https://support.microsoft.com/en-us/kb/884538
If there is hope, then to open this buggy file, you must either manually delve into binary code or to have a special app to open damaged cdr files...I from my experience  can recommend a good program CDR Repair KIT for this. Hope I helped you!) http://www.cdr.repair/
Also, I think that this information will be useful to you.
https://forums.techguy.org/threads/solved-problems-with-corel-drow.1137209/Thank you all for your advice! The issue has been resolved.
Good news...what fixed it BTW / ?