Are you aware that Forms 10 was desupported long before Win8 was released? Were you also not aware that Forms/Reports 10 is hardly even supported to be installed on Win7? There are various reasons why this version won't work correctly on Win8, but if you feel that you want to make it work your best chance of doing this would be to follow MyOracleSupport note 559067.1. This note explains how to install 10.1.2.3 on Win7.
Also, for everyone's benefit... at this time, no Forms/Reports versions are supported on Windows 8 or Windows 2012. For the latest certification information be sure to follow each product version's Certification Guide:
But I've created many forms those are running smoothly. I am fetching this problem only in 3 .fmb while opening them.
Can you tell me why some .fmb working and why some .fmb not working?
It should not work totally If it's not supported in Windows 8.
Now My question why it's working partially.
Your statement about "it should totally not work" is not true. You will find that trying to use 10.1.2.0 on Win7 or Win8 will work for some things but fail for others. As I mentioned, your best chance for success will be to follow the instructions provided in the MyOracleSupport document I mentioned. If you do not have access to MOS, you will not be able to access the document.
Since version 10 is not certified to be used on Win8, I will not be commenting further as I do not recommend using this old (desupported) product on a brand new OS. Even if you get are able to make it appear as if it is working, you will likely experience other issues as you go forward.
Do the forms crashing the forms builder have compile errors? There is a patch for developer suite solving a problem which crashes the forms builder when opening a form with compile errors under windows vista; I had the very same problem on windows 7 and as windows 8 and windows 7 are not that different you might hit that problem too. Search on MOS for the patch.
Note that this might not only be caused by code in the form itself but also by invalid database procedures etc.
I am having a similar problem and I have NOT tried to troubleshoot the issue. What I believe is the cause of my problem is that something that was passed during one of the Microsoft Windows Updates has caused the problem. I would suspect that by un-installing and re-installing the development suite following [url https://forums.oracle.com/forums/thread.jspa?messageID=9256227�]the information here should help. However, I also believe that it is something that will have to be done again and again as Microsoft releases updates that break the developer suite.