Below is a list of the OraForms errors that can be thrown by the OraForms API calls.
| ID | Message | Description |
|---|---|---|
| 1 | Logon dialog not found | OraFormsLogon and OraFormsLogonCancel can throw this error if the Logon dialog is not the current active dialog. It is most likely that the OraFormsConnect failed because the logon dialog should be the first dialog after a successful connect. |
| 2 | Window not found | OraForms-CloseWindow, -WindowMove, -WindowResize and -WindowUpdate will throw this error if the window with the passed window name/ID has not yet been created. Similar to the 5 - handler not found error message. |
| 3 | Unsupported property | Can be thrown by multiple OraForms calls when the calls are querying handlers for special properties that should be set but are not. This error is not likely to happen under normal circumstances. |
| 4 | Focus handler not found | OraFormsSetFocus throws this error if the handler with the passed handler name/id was not found. Similar to the 5 - handler not found error message. |
| 5 | Handler not found |
This method can be thrown by any OraForms API call that takes a handler name/ID as first parameter. The first thing that every API call verifies is if the handler with the passed name/ID has already been created. If not, the operation cannot be executed on that handler. There are multiple reasons why a handler is not present during replay although it was during recording. The most common case is that an error was raised on the server, for example because of invalid user input. This invalid input has caused the application to not display dialogs or other windows that would normally appear when entering valid data like it does during recording. |
| 6 | The button to be pressed does not exist | OraFormsMessageBoxButton throws this error if an invalid button number was passed to the method. Valid buttons are: ORA_ ALERT_YES, ORA_ALERT_NO, ORA_ALERT_CANCEL. |
| 7 | Menu item was not found | OraFormsMenuItem throws this error if the menu item passed by its full name was not found. The menu item is searched in the assigned menu of the passed window name/ID. |
| 8 | Tab page not found | OraFormsTabSelect throws this error if there is no tab page with the passed name or passed index. |
| 9 | Unrecognized dialog button | OraFormsCloseDialog throws this error if an invalid button number was passed to the method. Valid buttons are: ORA_DIALOG_OK and ORA_ DIALOG_CANCEL. |
| 10 | The function cannot be applied for this handler | Several OraForms API calls throw this error if the method was called on a handler of a type that does not allow to execute that kind of function,for example OraFormsTabSelect on a non-tab control handler. |
| 11 | The LOV row does not exist | OraFormsLovSelect throws this error if there is no entry in the current list of values dialog that matches the passed name or passed row index. |
| 12 | The list item does not exist | OraFormsListSelect and OraFormsListActivated throw this error if the list handler referenced in the first parameter does not contain a list element with the passed value or index. |
| 13 | Handler is of invalid class | Several OraForms API calls throw this error if the method was called on a handler of a type that does not allow to execute that kind of function, for example OraFormsTabSelect on a non-tab control handler. |
| 14 | A value for this property is not set | All OraFormsGetProp{Type} methods throw this error if the requested property has not been set on the passed handler. |
| 15 | Array index is out of bound | OraFormsGetPropStringArray and OraFormsGetPropByteArray throw this error if the passed element index is out of the array boundaries of this property. Use OraFormsGetPropStringArrayLen and OraFormsGetPropByteArrayLen to get the number of elements in the array. The index is 0-based. |
| 16 | Verification failed | Every verification function throws this error if the defined verification fails. |
| 17 | Received version too old | If the server returns the error VERSION_TOO_OLD during the connect phase, this error is thrown. This means that the version number of the client is too old to work with the version on the server. Use a different version number for the client by customizing the OraFormsSetInt for the property INITIAL_VERSION or the version number in the profile settings. |
| 18 | Received version too new | If the server returns the error VERSION_TOO_NEW during the connect phase, this error is thrown. This means that the version number of the client is too new to work with the version on the server. Use a different version number for the client by customizing the OraFormsSetInt for the property INITIAL_VERSION or the version number in the profile settings. |
| 19 | Alert dialog | Whenever an alert dialog is created, this error is thrown. The default severity of this error is INFORMATIONAL as alert dialogs are often used as the normal way to display a message to a user. |
| 20 | Statusbar changed | Whenever the server updates the status bar text, this error is raised with the new text of the status bar. The default severity is INFORMATIONAL as a status bar update is normally a way to inform the user about server side actions, but it could also be an error message. Therefore, when doing root cause analysis of errors check for status bar changes. |
| 21 | Runtime error, see log file for stack trace | If there are internal replay runtime errors, this error is logged with a detailed stack trace in the replay log file. In case of such an error, contact technical support and send all recorded and replayed files. |
| 22 | WINSYS_BEEP | This error is logged if the server sends a WINSYS_BEEP message. Oracle Forms applications send a WINSYS_ BEEP to indicate that the last action caused some problems on the server, for example invalid user input. It is likely that a WINSYS_BEEP is followed by other errors like Handler not found. The reason for this is because a recorded session without errors could cause errors during replay if the script is customized with invalid input values, or if a script that should be customized is not customized, for example using different values each time a test is run. |
| 23 | OraFormsSetConnectMode overrides the profile's connection setting | This is just a warning indicating that the setting in the profile is overruled by the scripted OraFormsSetConnectMode. |
| 24 | Profile setting INITIAL_ VERSION overridden by function OraFormsSetInt | This is just a warning indicating that the setting in the profile is overruled by the scripted OraFormsSetInt ("INITIAL_ VERSION", version). |
| 25 | Verification succeeded | Whenever verification succeeds, a success log entry is created. |
| 26 | Handler already destroyed or not created yet | It is possible that the client applet sends messages from special handlers (controls) that are already officially destroyed by a destroy message from the server. This is not a real error and can only occur during recording. Therefore, a warning is logged. |
| 27 | Tree item was not found | All OraFormsTree API calls throw this error if the referenced tree item was not found in the tree. |