may be bugs in the software causes the first issue..?
What is your exact Forms version (eg: 10.1.2.0.2, etc). This could be a bug in the Forms Builder, but it actually sounds more like you have inherited (subclassed) objects in your form and the Forms Builder can't find the source of the subclassed objects. Do you get an error when you open the form that indicates the Forms Builder can't find files?
Thanks for answer me
the version of the form builder is 10.1.2.0.2 , and i did not get any error when i open the form..
what should be do please.
Are you subclassing these objects? If so, double-check the source object file to ensure it is OK. If your item is not subclassed, it could be that the property value is having problems. Try restoring the property to its default value (open the property pallet on the item, select the Height/Width properties, click the "Inherit" button in the Property Pallet toolbar). Once you have reset the affected property to its default value - save - exit - and reopen your form to see if that corrects the problem. If it does, change the properties back to their desired value.
If this still doesn't correct the problem, the only other thing I can think to try is to convert your form to a text file (.fmt) or to xml and then re-import from either of these formats. To export your form to a Forms Text File (.fmt) follow these steps:
- From the Forms Builder Menu click on the File menu and select the Convert option.
- From the Convert dialog box, choose:
- Type = Form (default property)
- Direction = Binary-to-Text
- Click Browse... button to select the file to convert.
- Click Convert.
This will convert your form to a .fmt format. I recommend closing the Forms Builder and restarting before converting the .fmt back to a .fmb. To convert the .fmt back to a .fmb follow the same steps listed above and change item 2.2 from "Binary-to-Text" to "Text-to-Binary".
To convert your Form to xml and back, follow these steps:
- Open a command (cmd.exe) window. This step is done manually.
- Navigate to your Developer Suite Home directory (typically: C:\DevSuiteHome_1)
- Navigate to the \BIN directory
- Run a directory listing of all Windows Batch Files (dir *.bat).
- Among the many batch files listed, you should see "frmf2xml.bat" and "frmxml2f.bat"
- This step simply confirms the batch files you need are available.
- Navigate to the directory where your Forms Binary file (.fmb) exists
- Run the following command:
- frmf2xml FORM_NAME.fmb
- For example, if your form name is MAIN_MENU.fmb and this file resides in the TEMP directory on your C-drive the command would be:
- C:\TEMP> frmf2xml MAIN_MENU.fmb
- This process takes a couple of minutes. If you receive an error this is most likely due to your environment variables not being setup correctly. Make sure your Oracle Home directory is listed in your PATH variable.
If you were able to successfully convert your file to xml, now convert it back to a Forms Binary as follows:
- While in the same directory, first make a back up copy of your original .fmb.
- type: rename FORM_NAME.fmb FORM_NAME.fmb.orig
- Now type: frmxml2f FORM_NAME.xml and press Enter.
- Again, you will see the Forms to XML Tool converting your .xml file
Once complete, try opening your newly converted Forms Binary in the Forms Builder to see if you still have the same problem.
If the problem persists after this, I recommend you open two instances of the Forms Builder (one with the problem form and one with a new Forms module) and copy all of the objects from the problem form to a new form and save this new form.
Hope this helps.