Http://www.itpub.net/thread-1927599-1-1.html
In the 64-bit win 7 environment, according to the oracle10g version of form Builder, the error message will appear when opened.
<ignore_js_op>
capture. PNG (29.24 KB, download number: 4)
Download attachments
Error content
2015-7-3 13:47 Upload
View the log details as follows: Issue signature: Issue Event name: Appcrash Application Name: Frmbld.exe Application Version: 10.1.2.0 application timestamp: 42d6363 2 Fault Module Name: KERNELBASE.dll failure module version: 6.1.7601.17965 fault module timestamp: 506dbe50 exception code: ebad198c Abnormal bias Move: 0000c41f OS version: 6.1.7601.2.1.0.256.1 Regional Settings id:2052 Additional information 1:200e additional information 2:200e C500b6815f859e4322ac3e81ebf6 Other Information 3:F0AD other information 4:f0ad4513401e148000010c6a2d5dde8a
Workaround 1:1) Download the Oracle Patch: P13413002_10105_WINNT 2) Configure the path variable, which contains the Opatch and Windows\System32 3) configuration oracle_home, pointing to 10g Dev 4) in the extracted p13413002_10105_winnt directory, running Opatch apply-no_inventory 5) During the operation, the system will be prompted several times: whether to continue, continue to the end, 6) Press the last hint, run the p1341 3002_10105_winnt\13413002\custom\scripts The Post.bat installation is complete, if there is no corresponding 10gDev home key group in the registry, you will need to create a new Forms_path variable. To point to the frm and PLL storage paths, avoid FRM-18108: Mount the following objects failed.
The above way is my colleague's way of handling, in this way he is OK, but I am in the execution of Opatch Apply-no_inventory is always unsuccessful. So I took the following 2nd way
Solution 2: Find other machines with the same machine configuration, but can open the form builder's colleague save a copy, and then use the saved form, you can open it. Although it is a more stupid way, but in emergency situations, and can not find a good solution, but also a quick way.
Solution 3: After being tortured for many days, occasionally found that after connecting to the database, and then open the file to find the appropriate form, the problem is resolved.
Form Builder opens large file Form report Appcrash error