Specification Codes from spc0000 to spc0049Official Content

The list that follows shows the message codes from spc0000 to spc00049 that can appear during Program Specification. The complete list can be found here.

 

Code
Message
 
 
%1
 
It is a generic message code that usually should not appear.
 
 
Control/object %1 not found/defined. Is it on the form?
 
It refers to a property/method of a control or object that could not be identified. Usually, it occurs when controls are deleted from/renamed in the Form but the references to them are not corrected in the rules/methods/subroutines.
 
Could also happens when a Transaction is specifying as Business Components; which contains a Rule or Event associated to a control in the form. The BC specification ignore the Transaction's form so the control could not be identified. You may enclose them in [Win]/[Web]/[Text] environment attributes to avoid this error.
 
To make this error message a warning see Check type errors property.
 
 
%1 object does not have the %2 property.
 
It refers to a property (%2) that is not supported by type object (%1).
 
 
Property ‘Component’ is deprecated.
 
The Component property is being used but it is no longer supported.
 
 
This object cannot be generated on this environment %1.
 
The environment (%1) does not support the object type.
Possible causes are:
a.     When specifying Work Panels in a Web environment. (*)
b.     When specifying Web Panels in a Win environment. (*)
c.     When specifying Master Page Web Panels and the generator does not support Master Pages.
d.     When specifying Business Component Transactions and the generator does not support Business Components.
e.     When specifying a Work panel, Menú or Menu Bar belonging to a module different from the root.
 
This can occur, for example, when a Web Panel calls a Work Panel or viceversa.
 
 
%1 objects do not have the ‘%2’ method.
 
It refers to the method (%2) that %1 type objects do not support.
 
To make this error message a warning see Check type errors property.
 
 
Assignment between objects %1 is not allowed.
 
The assignment between "object" type variables (such as Httpresponse) is not supported. 
 
 
Call to program %1 that cannot be generated or accessed (URL Access = No)
 
The call to program %1 could not be generated for one of these reasons:
a.     The %1 program cannot be generated in the defined environment. Quite probably, if the %1 program is specified, the spc0005 message will appear. 
b.     The %1 program is a Web Component (Transaction or Web Panel) with the “URL Access” property in “No.” In this case, it is not possible to have a Call, Link (the command) or Submit to this object.
 
 
Type mismatch in %1: %2.
 
A type error occurred in %1 whose value can be expression, condition, assignment, etc. %2 presents additional information that allows identifying the error. 
 
To make this error message a warning see Check type errors property.
 
 
Type mismatch in assignment: %1 = %2 (%3=%4).
 
A type error occurred in an assignment. %1, of the %3 data type, does not support to be assigned %2, which has the %4 data type. 
 
To make this error message a warning see Check type errors property.
 
 
Type mismatch in rule %1.
 
The rule identified by %1 does not support the data type of the parameters specified to it. 
 
To make this error message a warning see Check type errors property.
 
 
Object %1 referenced in a Create function must be a component. Did you specify it?
 
The first parameter of the Create() function must be an object with the Web Component property in Yes. The message can appear even when the object has the Web Component property in Yes, if it has not been specified yet.
 
 
Use %1 instead of %2 %3.
 
It suggests the use of the %2 super-type instead of the %1 subtype in a group or grid (%3) since using the super-type may cause ambiguity. 
 
 
Cannot update table %1 when using a temporary index.
 
It applies to generators other than SQL (RPG, Cobol, etc.) avoiding updates when a temporary index is being used.
 
 
Invalid rule syntax: %1
 
It is an internal error that usually should not occur. It can occur if a specifier of previous versions is being executed in newer versions of GeneXus.
 
 
Invalid condition syntax: %1
 
It is an internal error that usually should not occur. It can occur if a specifier of previous versions is being executed in newer versions of GeneXus. 
 
 
Expression %1 does not return a value.
 
The expression identified in %1 does not return a value. E.g.: This can occur when trying to assign the result of a method that does not return values to a variable/attribute.
 
As from GeneXus X Evolution 1 Upgrade 3, this control has been extended to Procedures, Data Providers and Web Components. For instance: 
  • &result = ProcWithoutParm()
  • WebComp.Object = WebPanelwithoutParm()
To make this error message a warning see Check type errors property.
 
 
Property %1 is read only. It cannot be assigned.
 
This error appears when your code is trying to assign the value of:
  • A property that cannot be modified
  • A Business Component member that is read-only.
 
Business Component members are read-only if any of the following is true:
  • They are inferred attributes
  • They have an unconditional noaccept rule
  • They are assigned in the Start Event of the Business Component
To make this error message a warning see Check type errors property.
 
 
%1 is not a valid value for parameter %2 of %3.
 
A non-supported value (%1) is being used for the %2 parameter of the %3 function. 
 
 
Line %1. Failed to expand dynamic call.
 
An error occurred when trying to expand a dynamic call in static calls. Usually, this error occurs when the list of parameters specified in the dynamic call could not be analyzed because of its complexity.
 
 
Line %1. No programs found matching dynamic %2 parameters.
 
It can occur when expanding dynamic Calls or Creates. It occurs when, in the Knowledge base, it has not been possible to find already specified programs matching the number and type of parameters indicated in the dynamic Call or Create.
 
 
Input parameter %1 cannot be assigned.
 
When trying to assign a variable/attribute defined as IN in the Parm() rule.
 
 
Parameter %1 %3 %2 has wrong type.
 
It indicates that a parameter that does not correspond to the one expected by the program referred to is being transferred in a Call, Submit, Link, Udf or Udp. 
 
 
Not enough parameters %2 %1.
 
The number of parameters specified in a Call, Submit, Link, Udf or Udp is lower than the one specified in the Parm() rule of the program referred to. 
In the case of submit command/method an aditional parameter is required as explained Submit method
 
 
Too many parameters %2 %1.
 
The number of parameters specified in a Call, Submit, Link,Udf or Udp is higher than the one specified in the Parm() rule of the program referred to. 
 
 
Formula %1 cannot be evaluated in this program.
 
The %1 vertical formula cannot be worked out in the program. This situation occurs because the navigation required to evaluate the formula conflicts with the navigation of the program using it.
 
 
No relationship found among attributes %3. Attributes: %1 are incompatible with: %2.
 
It has not been possible to find a way to solve the navigation for the attributes mentioned in %1 and %2. The incompatibility information is not necessarily strict, it is actually a guide.
 
Tip: if the message includes "control" (i.e. “No relationship found among attributes in control %3…”) the problem could be caused by a "dynamic combo box with conditions," check the Attribute control type definition.
 
 
Attribute %1 is part of the index. It cannot be updated.
 
The attributes making up the index that is being used to navigate cannot be updated unless the access to data is made with SQL.
 
 
Attribute %1 is part of the primary key. It cannot be updated.
 
A table primary key cannot be modified.
 
 
Line %2. Attribute %1 should not be assigned in an insert group. It has the Autonumber property set to on.
 
Attributes with the Autonumber property in On do not need to be assigned to the New groups or to transactions. The assignment is ignored but it can be used in environments where the Autonumber property is not natively supported.
 
 
No relationship found among attributes %1.
 
It applies to New groups and is similar to the case of the spc0027 message.
 
This could be due to the following causes:
§   The same as spc0027 in New-EndNEw groups.
§   When the object includes a control attribute that is not supported by the target generator. For example: a Dynamic Combo Box using attribute formula as "Description attribute" or requiring a multi-table navigation in VB. %1 is the control name.
 
 
&Mode cannot be assigned in this type of objects.
 
The &Mode variable cannot be modified in transactions. 
 
 
%1 will be read only in update mode.
 
It occurs when updating data in tables superordinated to the base table of a transaction. The %1 attribute is part of the key of those tables that are being updated. 
 
 
Syntax error in: %1. Ignored.
 
It is an internal generic error that usually should not occur. It can occur if a specifier of previous versions is being executed in newer GeneXus versions.
 
 
Line %4. The program %1 that implements property %2 of data type %3 does not exist in this model.
 
It applies to the user data types (such as the Workflow data types) when the GeneXus object handling this property does not exist in the knowledge base.
 
 
Line %4. The program %1 that implements method %2 of data type %3 does not exist in this model.
 
It applies to the user data types (such as the Workflow data types) when the GeneXus object handling this method does not exist in the knowledge base.
 
 
%1 cannot be inferred.
 
It occurs when GeneXus cannot navigate the %1 attribute that is a subtype. The attribute value is undefined and could vary from one specification to the other.
 
 
There is no index for order %1 in group starting at line XXX.
 
It is a warning that indicates that as long as many records exist in table (or the number of records selected from the table is important), performance can be bad, and this could be caused by the lack of an index according to the indicated criteria.
 
 
Ambiguous reference to attribute %1. Subtype group %G1 instead of %G2 chosen this time.
 
It occurs when making a reference to the %1 super-type and there are several ways to instance it (several subtypes). The specifier chooses one of the possible ways (subtype groups %G1 or directly by the supertype (“none” appears in this case instead of the group name). The chosen way can vary from one specification to the other.  We suggest defining a subtype for the %1 attribute and using it to guarantee consistency among specifications.
 
 
Subtype group %1 contains secondary attributes (%2). Secondary attributes ignored.
 
The definition of the %1 subtype group contains attributes (%2) that cannot be determined by the primary attributes of the same group (called secondary attributes). The definition of subtypes for these attributes is ignored, that means %2 attributes could not be inferred.
 
 
Subtype group %1 does not have primary attributes. Subtype group definition ignored.
 
The definition of the %1 subtype group lacks primary attributes thus making it impossible to use it. The definition of subtypes for these attributes is ignored.
 
 
Subtype group %1 (%2) does not identify a base table. Subtype group definition ignored.
 
Primary attributes of the %1 subtype group do not coincide with the primary key of any of the model tables. The definition of subtypes for these attributes is ignored.
 
 
%1 is not instantiated %2.
 
It is a warning message that can occur in several situations. In all these cases, the attribute value is undefined.
·          New/XNew groups that make reference to attributes that cannot be instantiated in the higher levels.
 
·          Attributes of the "flat" part (which do not belong to any grid) of Work and Web Panels, with multiple grids, for which it has not been possible to establish navigation.
 
·          Attributes of subordinated levels that could not be instantiated in the higher levels.
 
 
%2 cannot be assigned in NEW group starting at line %1.
 
The %2 attribute is being assigned in a New group, and it does not belong to the base table of this New.
 
 
Object %1 referenced by control %2 must be a component.
 
The object referred to in the Object property of a WebComponent type control must have the Web Component property in Yes. 
 
The validation is made against the last specification of the program referred to; thus, the problem could be corrected by specifying the program referred to and then the caller again.
 
 
Variable %1 not defined. Same as %2 assumed.
 
The variable mentioned in %1 has not been defined. It is assumed equal to the %2 attribute because they have the same name.
 
 
Variable %1 not defined; %2 assumed.
 
The variable mentioned in %1 has not been defined. The %2 definition, which was inferred from the first assignment to %1, is assumed.
 
 
Attribute(s) %1 is(are) defined in table %2 but not in Data view %3.
 
It occurs when accessing the Data View %3 associated to the %2 table, and the mapping for the %1 attribute(s) has not been defined yet.
 
 
Not used
 
 

Next

 

 


Was this page helpful?
What Is This?
Your feedback about this content is important. Let us know what you think.