Code

Description

O101

Requested resource not found during CREATE of an object. Resource DLL cannot be open in two (2) programs at the same time.

O102

Requested PICT or MOVIE file not found during CREATE of an object.

O103

Windows system error during CREATE of an object. Possible causes of this error could be the lack of available memory, the lack of system resources to allow creation of the object, improper data in variable for CREATE or points to a DLL that does not exist.

If the error was on a CREATE DIALOG instruction, an additional subcode is provided in the form of 'nnmm' where nn is the dialog item being processed and mm is the actual error. The following are the possible values of mm:

01: An = or : was expected but not found.

02: A ' was missing on a name.

03: Out of memory.

04: A position t:b:l:r was malformed.

05: Dialog type was not MODAL, MODELESS, or PROGRESS.

06: Dialog POS or ABSPOS values were malformed.

07: Undefined Dialog string operation encountered.

08: Unable to load an ICON.

09: Too many items in Dialog.

10: Missing comma separator.

100: PLB FORM value is too large for .NET data variable.

101: PLB FORM negative value is invalid for the .NET data type.

O104

Screen dimensions are too small to allow an object to be created.

O105

CREATE instruction must be executed for an object before an ACTIVATE instruction may be used or the object is specified.

O106

Insufficient memory is available to perform operation.

1. Check the 'virtual memory' configured under Window's 'Control Panel' in 'Enhanced 386 Mode'. It is recommended that virtual memory be defined as permanent and at least 4 MB should be defined.

2. Check Windows system resources. If the system resources percentage is very low, other Windows programs may need to be terminated.

3. The -mNNN option for the runtime PLBWIN allocates less than the default 1 MB amount of memory. The NNN value may be specified to something less than this to save memory requirements.

O107

A dialog number not associated with a POPUPMENU or a DATALIST dialog item was specified for a DELETITEM instruction.

O108

Invalid font specified. Subcodes further identify the problem as follows:

21: Unable to allocate memory.

22: Unable to locate font or font not valid for requested device.

23: Unable to create working font.

24: Font in single quotes not terminated.

25: Font name not valid internal name or does not start with '>' character.

26: Invalid options in parenthesis.

27: Invalid options string not terminated properly.

28: Invalid options string not terminated properly.

29: Invalid font name extra data at end of name.

O109

Too many MODAL dialogs have been activated at the same time. Only ten MODAL dialogs may be activated in a nested manner.

O110

Deactivation of nested MODAL dialog is not being performed in reverse order of activation. When MODAL dialogs are activated in a nested manner, they must be deactivated in the reverse order of activation.

The ObjectID property value of the WINDOW object generating the ERROR is specified as a SubCode value as shown:

ERROR Sub Code: nnnnnn

The ObjectID property value of the current active WINDOW object is specified in the extended data as shown:

Extended Data: ObjectId: mmmmm

O111

WINAPI error where the function specified in the PROFILE declaration could not be found. Make sure the spelling of the API function name is correct. If the name appears to be correct, the cause may be that the function is a UNICODE enabled function that requires that the API function name has a character 'A' or 'W' appended to it. A UNICODE enabled function may be determined when a parameter of the API function is a string variable. The 'A' character indicates that the string parameters contain ASCIIZ data. The 'W' indicates that the string parameters contain UNICODE string data.

O112

WINAPI error where an invalid parameter was passed in for the function specified in the PROFILE declaration. Verify that the variable type specified in the PROFILE declaration is consistent with the required parameters of the API function.

O113

WINAPI error where an invalid result variable was assigned for the function specified in the PROFILE declaration. Verify that the variable type specified in the PROFILE declaration is consistent with the return variable of the API function.

O114

WINAPI error where the DLL module name specified in the PROFILE declaration was not loaded or is invalid. For user generated DLL modules, the program must first execute the Windows 'LoadLibrary' function to load the DLL module before an API function may be executed. The Windows 'FreeLibrary' function must be executed by the user program to unload the DLL module. Basic Window's API modules (kernel32, user32, & gdi32) do not have to be loaded using the 'LoadLibrary' function. This only applies to special or user created API modules. When executing on a client attached to a Linux/Linux server, ensure that the function name in the PROFILE statement begins with an exclamation mark(!), This causes the function to be loaded from the client rather than the server.

O115

Invalid tab stop value in a DATALIST object.

O116

DATALIST object is full.

O117

COMBOBOX object is full.

O118

MODELESS dialog cannot be activated on top of a MODAL dialog.

O119

FORMLOAD operation failed. Subcodes further identify the problem as follows:

20: Invalid form creation data for window object.

21: Invalid form window object.

22: Unable to identify form object.

23: Invalid form creation data for object.

24: Invalid object type found for form.

26: Invalid form internal data variable.

27: Invalid form internal data variable.

28: Invalid form internal data variable.

29: Invalid form internal data variable.

30: Invalid form internal data variable.

31: Unable to locate form register event code description data.

32: Unable to read form register event code description data.

33: Unable to locate form register event name data.

34: Unable to read form register event name data.

35: Unable to read form resource Id count data.

36: Unable to locate form header data.

37: Unable to read form header data.

38: Unable to locate form data.

39: Unable to read form data.

40: Invalid form identification string.

41: Invalid form version found.

42: Invalid form completion flag.

43: Unable to locate form name data.

44: Unable to read form name data.

44: Unable to locate form startup data.

45: Unable to read form startup data.

46: Form must be an objects-only form.

O120

Too many items in COLLECTION.

O121

A WINDOW object specified for the PARENTWIN property has not been created.

O122

Operation being performed that is not supported for PLBCE runtime.

O123

Specified property does not exist for object.

O124

Too many parameters have been specified for an object method or a WINAPI instruction. For the WINAPI instruction, any API function parameter type requiring an INT8 PLB data type counts as two (2) parameters toward the maximum of twenty (20) parameters supported.

O125

There is a problem with a method name, with one of the parameter names, or parameter names are not allowed at all.

O126

Invalid parameter type specified for a method.

O127

Method does not provide a result yet a result is being requested.

O128

Required parameter is missing from method parameter list.

O129

Duplicate method parameter specified.

O130

Invalid parameter name specified.

O131

More than 200 string properties (*property=<value>)are being used for one CREATE statement.

O132

Unable to convert VARIANT data type to PLB data type variable.

O133

Invalid variant type specified for VARIANT object create. This error can also occur when a SETPROP of the VARTYPE property for a VARIANT object specifies a $VT_ARRAY value.

O134

The window specified as a parent window is invalid when using the PARENTWIN property. The window operand for the PARENTWIN property cannot have a window type of MODAL or MODELESS.

O135

Invalid argument requested for an EVENTINFO or EVENTREG.

O136

No more than ten (10) nested collection name references are allowed for an OLE object.

O137

No more than one hundred (100) collection index reference strings are allowed for an OLE object.

O138

Null collection name reference is invalid for an OLE object.

O139

Method does not exist for AUTOMATION interface.

O140

Collection name reference does not exist for an OLE object.

O141

Unable to invoke a method for an OLE object. Additional error data is not available. Possible causes could be an indeterminate number of reasons.

O142

Collection index reference is invalid for OLE object.

O143

The number of parameters is different from the number of arguments accepted by the method or property.

O144

One of the parameters is not a valid variant type.

O145

The OLE application has caused an exception error. Information concerning the exception error may be available by using the GETINFO EXCEPTION statement.

O146

The specified member (method/property) does not exist or the operation tried to set the value of a read-only property.

O147

This implementation of the IDispatch interface does not support named arguments.

O148

One of the arguments could not be coerced to the required type.

O149

One of the parameter DISPIDs being specified is invalid for the method. An 'ARG:' extended error data should indicate the first argument that contains the error. The 'ARG:' extended data is either presented in the error dialog or appended to the error variable for a TRAP operation.

O150

One or more of the arguments contained invalid data type that could not be coerced into the required type format. The index within the argument list of the first parameter with the incorrect type is supplied as 'ARG:' extended data. The 'ARG:' extended data is either presented in the error dialog or appended to the error variable for a TRAP operation.

O151

The member being invoked interprets string arguments according to the LCID, and the LCID is not recognized. If the LCID is not needed to interpret arguments, this error should not occur. LCID refers to 'Locale Identifier'. This specifies language requirements to member operations.

O152

A required parameter was omitted.

O153

an OLE object can not be created. The following are valid subcodes allowed for this error.

100: Runtime does NOT support OLE.

101: Unable to establish storage id because more than 300 OLE objects have been created.

102: Unable to establish OLE form setup requirements.

103: Unable to create OLE container object because of invalid class or required interfaces are not available.

104: Unable to create OLE control object because of invalid class or required interfaces are not available. The Windows Extended error code is provided when it is available to be reported. In this case, the WINERR value in an extended OLE error that can help to identify the cause of the error.

110: CLASSID was not specified.

O155

ADMIN operation failed. Subcodes further identify the problem as follows:

1: Failed to start socket

2: Bad IP number

3: Out of memory.

4: Socket create failed

5: Socket bind failed

6: Admin not found

7: Bad version

8: Unknown version

9: Connection lost

10: Socket error

11: Encrypt startup

O156

A bad access error occurred performing an operation on a VARIANT object when using/expecting a variant array type.

O158

An IMAGELIST is being used as a property {value} before it has been created.

O159

An invalid data variable type has been encountered for a GETPROP or SETPROP property {value}.

O160

The source and destination GUI Object variables in a MOVE object to object operation do not have the same object types.

O161

A SUBMENU was activated and the parent {menu} object has not been created or set.

O162

An invalid GUI object was used in a PL/B instruction.

O163

Unable to convert VARIANT data type to PLB data type variable because the VARIANT contains a VT_NULL variant type.

O164

Invalid event specified for a NETOBJECT or NETCONTROL.

O165

Unable to convert a .NET data type for the operation.

O166

The client version does not support the STREAM instruction.

O199

A GPF error has occurred in a Windows OS function while executing a PL/B method.