Code

Message

Program Specification Message

spc0000

%1

It is a generic message code that usually should not appear.

spc0001

Control/object %1 not found/defined. Is it on the form?

It makes a reference to a property/method of a control or object that could not be identified. Usually, it occurs when controls are eliminated/renamed in the Form but the references to them are not corrected in the rules/methods/subroutines.

spc0002

%1 objects does not have the %2 property.

It makes a reference to a property (%2) that is not supported by %1 type objects.

spc0003

Property ‘Component’ is deprecated.

The Component property is being used and is no longer supported.

spc0005

This object cannot be generated on this environment.

The environment 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 Pages Web Panels and the generator does not support Master Pages.

d.       When specifying Business Components Transactions and the generator does not support Business Components.

spc0006

%1 objects does not have the ‘%2’ method.

It makes a reference to the method  (%2) that %1 type objects do not support.

spc0007

Assignment between objects %1 is not allowed.

The assignment between "object" type variables (such as Httpresponse) is not supported. 

spc0008

Call to program %1 that cannot be generated.

The call to the program %1 could not be generated for one of this reason:

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, is not possible to have a Call, Link or Submit to this object.

spc0009

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. 

spc0010

Type mismatch in assignment: %1 = %2 (%3=%4).

A type error occurred in an assignment. %1, which has the %3 data type, does not support to be assigned %2, which has the %4 data type. 

spc0011

Type mismatch in rule %1.

The rule identified by %1 does not support the data type of the parameters specified to it. 

spc0012

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.

spc0013

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. 

spc0014

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.

spc0015

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 GeneXus newer versions.

spc0016

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 GeneXus newer versions. 

spc0017

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. 

spc0018

Property %1 is read only. It can not be assigned.

When trying to assign a property that cannot be modified. 

If the property “Check Type Errors” has the “Yes” value, this message will be displayed as Error, otherwise it is a Warning.

spc0019

%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. 

spc0020

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.

spc0021

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.

spc0022

Input parameter %1 cannot be assigned.

When trying to assign a variable/attribute defined as IN in the Parm() rule.

spc0023

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, Udf or Udp.  

The validation is made against the last specification of the called program; thus, the problem could be corrected by specifying the called program and then again the caller.

spc0024

Not enough parameters %2 %1.

The number of parameters specified in a Call, Submit, Udf or Udp is lower than the one specified in the Parm() rule of the program referred to. 

The validation is made against the last specification of the called program; thus, the problem could be corrected by specifying the called program and then again the caller.

spc0025

Too many parameters %2 %1.

The number of parameters specified in a Call, Submit, Udf or Udp is higher than the one specified in the Parm() rule of the program referred to. 

The validation is made against the last specification of the called program; thus, the problem could be corrected by specifying the called program and then again the caller.

spc0026

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 is in conflict with the navigation of the program using it.

spc0027

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 really a guide (working it out exactly could take a long time).

spc0028

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.

spc0029

Attribute %1 is part of the primary key. It cannot be updated.

A table primary key cannot be modified.

spc0030

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.

spc0031

No relationship found among attributes %1.

It applies to New groups and is similar to the case of the spc0027 message.

spc0032

&Mode cannot be assigned in this type of objects.

The &Mode variable cannot be modified in transactions. 

spc0033

%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. 

spc0034

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.

spc0035

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.

spc0036

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 knowledge base.

spc0037

%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.

spc0038

There is no index for order %1 on table %2; poor performance may be noticed.

It is a warning that indicates that as long as many records exist in %2 table (or the number of records selected from the %2 table is important), the performance can be bad, and this could be caused by the lack of an index according to the indicated criteria.

spc0039

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 the consistency among specifications.

spc0040

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 mean, %2 attributes could not be inferred.

spc0041

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.

spc0042

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.

spc0043

%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.

spc0044

%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.

spc0045

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 again the caller.

spc0046

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.

spc0047

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.

spc0048

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.

spc0050

Inferred subtype %1, cannot be assigned.

It indicates if an attempt to update subtype %1, which is inferred, is occurring and if there is any cause that makes this not possible. The cause may be that the subtypes-supertypes group is wrong or that it belongs to the *None group.

spc0051

Supertype %1 cannot be instantiated. Use subtype %2 instead %3

It indicates that supertype %1 (inferred) cannot be instantiated and suggest using subtype %2 instead. %3 is used as a reference to identify the problem and its message may be: "in group starting at row xxx" or "in grid "xxx"' depending on the circumstances. 

The reason for this is that there is at least one access by subtype to the group to which %2 belongs and, in the code, there is a reference to %1 (supertype of %2) instead of to %2.  The specifier can detect the situation, but it cannot correct it, as it could be expected, generating this message.

spc0052

Attribute %1 must be present on the screen or assigned by a rule.

It occurs when the attributes making up the primary key in a Transaction are neither present in the form nor assigned in the rules.

spc0053

Unsupported conditional constraint %1 changed to standard constraint %2.

It occurs when the generator does not support conditional constraints or when the condition is not evaluated by the DBMS.  It will be transformed into a “standard” restriction replacing the WHEN by a OR.

%1 is the specified condition and %2 is the group (For each) or grid where the change was made.

spc0054

Unsupported conditional order %2. Using default order in %1.

It occurs when the generator does not support conditional orders.  The navigation order will be the specified as unconditional order, or, if there were not it,  the primary key of the base table of the For each group.

%1 is the list of ordering attributes. %2 is the For each group or grid where the change was made.

spc0055

Conditional order in group starting at line %1 not allowed (Break group).

%1 is the line number of the For each group or grid where the situation was detected.

spc0056

Internal error. Variable %1 definition is incorrect or not available. Data:%2.

It occurs when we distribute an object that has variables that are structures and it is consolidated to a model that does not contain the definition of these structures.

spc0057

Internal error. Incorrect order clause syntax.

This is an internal error. If it occurs, please send a distribution of the KB, thus enabling the reproduction of the error to your local support.

spc0058

%1 must be an array or collection.

It occurs when making a reference to a variable that is not Array or Collection type in the command  For %2 in %1.

spc0059

Table %1 with two different orders.

It occurs when navigating to the same table (%1) by different orders and the generator does not support this.

spc0060

The program may be called by another program and the Commit on Exit property is set to YES.

It occurs when there is a Procedure that makes a database update with the  “Commit on Exit” property in “Yes” and it is called by another object. 

The warning is mainly due to two reasons: 

a.       Because, in fact, the intention is that the called object be included in the caller’s UTL and, as the “Commit on Exit” property has its default value, the procedure will do commit of all the pending changes to be made to the Database since the last commit.

b.       Because when the procedure that does commit is called from a For Each making an update, an error will occur (in any DBMS) on account of cursors closing. Therefore, in this case, the Procedure can neither have this property in YES nor do a commit explicitly. For more information please refer to the corresponding documentation.

spc0061

Group without attributes starting at line 1.

It occurs when there is a For Each group without attributes.

spc0062

Order none %1 not allowed (Break group).

It occurs when any For Each participating in the Control Break has the Orden None clause.

spc0063

Cannot perform updates when using the Distinct option

When using the Option Distinct in a For Each it is not possible to make an update within the For Each group (or in Breaks that are children of the one with the Option Distinct). The reason for this is that each row returned by the For Each has not necessarily only one database row associated (usually it has several).

spc0064

Option DISTINCT not supported in this environment.

The Option DISTINCT is only supported for generators accessing the database with SQL.

spc0065

Option DISTINCT cannot be specified in BREAK groups.

The Option DISTINCT is only supported in the first For Each of a For Each group defining Breaks. To solve the problem, we only need to move the code  (Option Distinct) to the first For Each of the group.

spc0066

Option DISTINCT not supported for local table %1.

The Option DISTINCT is only supported for tables accessed via SQL.

spc0068

This object does not support ‘%2’ data type parameters (%1).

A (%2) data type has been specified for a parameter that is not supported by this object type. E.g.: Web Panels and Main programs with Call protocol ‘Command line’ do not support Collections or SDTs or Arrays as parameters.

spc0069

When duplicate code will never execute. There are no updates to any attribute of a unique index.

The ‘When Duplicate’ command has been specified in the context of a  'For Each' (XFor Each or XFor First). Nevertheless, no attribute that is part of a unique index is being updated. In this context, the code will never execute.

spc0070

No When duplicate code found to handle possible duplicate condition when updating %1.

An attribute that is part of a unique index is being updated in the context of a For Each (XFor Each o XFor First). The new value may produce a duplicate key, and there is no code to handle it.

spc0071

%1 cannot be displayed or printed due to its data type (%2).

Variables with %2 data type cannot be present in the form or print block. For example a Structured Data Type variable (SDT).

spc0072

External %3 index not defined for attribute(s) %1 in Data View %2.

No mapping was found for a required index of type %3 (Primary key/Unique/Duplicate) on attribute(s) %1 for Data view %2.

Required Data View indices are:

§          All associated table indices when the access method is not SQL.

§          Primary key index when the access method is SQL and the program is performing any update on the associated table.

§          Unique indexes when the access method is SQL and the program is performing updates or deletes on the associated table.

Please check platform specific information, composition and type of all indexes on Data view %2.

spc0073

Formula %1 is invalid.

%1 is the name of an attribute defined as a formula. A valid navigation to evaluate the formula cannot be found. If %1 is a conditional aggregate the probable cause of the problem is that navigation involves more than one table.

For example, this error can be present if we have a sum aggregate over inferred subtype.

spc0074

Join to table %1 may not perform well as there is no index on %1's primary key.

Table %1 is associated to a Data view and no matching index was found for its primary key on its associated Data View. This may lead to slow join performance if table %1 has a large number of rows.

Please check platform specific information, composition and type of the primary key table %1 associated Data view.

spc0075

Operand %1 does not match the data type of %2 in the IN comparison.

%1 cannot be compared to %2. Comparison is carried out using the IN logical operator.

Please change data types as appropriate.

spc0076

%1 must be a collection to be used as the right operand in an IN comparison.

%1 is the right operand of an IN operator. It must be a collection or array.

Please define %1 as an array or collection.

spc0077

%1’s data type (%2) is not supported in an IN comparison.

%1 is the left operand of an IN operator. Its data type (%2) must be either Numeric, Character, VarChar, Date or Date Time.

spc0078

Internal error. Line %1 not recognized as a command.

This error should not occur. The source line %1 contains code that could not be recognized/parsed by Genexus Specifier.

Please contact support.

spc0079

Attribute(s) %2 in subtype group %1 is (are) not associated to any table.

Attribute(s) %2 is (are) primary attributes in group %2. As it (they) is (are) not associated to any table GeneXus does not know how to infer them. The subtype group is not valid.

This warning message usually occurs when a Subtype group is no longer in use or has been defined and imported from other Knowledge bases.

To solve this problem you may remove the Subtype group or reference the attribute(s) specified in the message in the appropriate Transaction.

spc0080

Attribute(s) %2 in subtype group %1 could not be solved.

The Subtype group %1 contains inferred attributes (%2) that cannot be "associated" to their stored counterpart.

Possible causes are:

a.       The ending stored counterpart (supertype) is not stored in any table.
You may solve this problem by removing the subtype definition for attributes %2 or checking why their corresponding supertypes are not stored.

b.       The subtype group does not have subtype definitions for foreign key attributes that determines %2 as in the following example that raises this warning (spc0080) for attribute ClientCategoryName:

Transactions

Subtype group

Adding ClientCategoryId as subtype of CategoryId in the subtype group and adding ClientCategoryId to the Client transaction solves the problem.

spc0081

Attributes %1 do not allow nulls in table %2 and are not referenced %3.

The list of attributes referenced in %1 do no allow nulls and the program been specified is trying to insert data without specifying values for them.

To fix the error you may:

a.       If the program is a transaction you may reference these attributes in the transaction structure or disable insertion in the appropriate level (use de “error() if insert” rule).

b.       If it is a procedure, the New group must reference them. Otherwise, you may change the nullability property of these attributes.

c.       Set the Initialize not referenced attributes property to Yes.

spc0082

Attribute %1 in table %2 does not allow nulls %3.

A null value could be assigned to attribute %1 and it does not support nulls in table %2. The error context is %3.

The nullvalue() function is assigned to attribute %1 and the "Generate null for nullvalue()" property is set to Yes.

You may remove the assignment, change the "Generate null for nullvalue()" property value or change the attribute nullability for this table.

spc0083

%1 not implemented by this generator.

The feature %1 is not available for the generator. You may choose another generator or try to achieve the same results without using this feature.

spc0084

%1 not implemented by this generator. Ignored.

This is an information message stating that the feature %1 is not available for the generator and can be ignored safely.

spc0085

Allownulls rule conflict with null definition for foreign key %1.

The foreign key %1 does not allow nulls as none of its attributes support nulls.

Remove the Allownulls rule (it should not be necessary) and change nullability of foreign key attributes as needed.

spc0086

Internal error. Wrong parameters information for program %1. Try saving it again. Problem data: %2, %3.

This error should only happen if redundant object parameters information is not found or is incorrect.

You should send the full message text and the root directory of your Knowledge Base to GeneXus support to fix the problem. Additionally, try saving the program %1 again and specify again.

spc0087

%1 language statements are used in this object.

This is a warning message stating that language specific statements are used in the program. It is useful when converting your application between languages.

spc0088

Grid %1 is associated to a collection. It cannot have navigation.

Grids associated to collections cannot have navigation (i.e. an implicit For Each). %1 is the control name of the Grid. It may be empty if you did not set it.

You should either remove any attributes from the Grid or from the Grid´s Load event.

Reorganization Message

rgz0001

Table name %1 exceeds maximum name length allowed by language (%2 characters).

The selected programming language cannot generate correctly with table names with more than %2 characters. The solution is to rename the table, change the programming language or change the method to access data.

rgz0002

Attribute name %1 exceeds maximum name length allowed by language (%2 characters).

The selected programming language cannot generate correctly with attribute names with more than %2 characters. The solution is to rename the attribute, change the programming language or change the method to access data.

rgz0003

Problems found on table %1 structure. It will not be created/reorganized.

This is a generic message that indicates that there were other problems preventing the table creation/reorganization. The other problems should appear in the impact analysis.

rgz0004

For each value of  %1 there could be several records of  %2 in table %3. Data may be lost.

This warning message indicates that two tables (one subordinated to the other) are "merging" into a unique table. E.g.: if we eliminate the detail in a typical Invoices transaction and we put the Product at Invoice level. In this example, the message indicates that only the Product in the first detail line will be kept in the reorganization; the remaining detail lines (and their Products) will be lost.

rgz0005

For each value of %1 there may be several values of %2.

This warning message occurs when a table is created from other table's data. E.g.: the creation of a Clients table from the Invoices table. In this example, the message indicates that per each value of the ClientCode there may be many values of the ClientName. Only one value of the ClientName table values will be kept per each value of the ClientCode; the rest will be lost.

rgz0006

AllowNulls=Yes for attribute %2 ignored. At least one attribute in foreign key %1 has the AllowNulls property set to No.

The %2 attribute is part of a foreign key made up with more attributes in the table that is being created/reorganized. The fact that some attributes of the foreign key can be null whereas other cannot be null is inconsistent. The solution is to give the same value (Yes or No) to the AllowNulls property of all foreign key attributes.

rgz0007

Attribute %1 does not allow nulls and has not a default value. An empty default value will be used.

It has been specified that the new %1 attribute does not allow nulls in the table that is being created/reorganized. Nevertheless, a value (or valid value) has not been specified in the Initial Value property. 

The message indicates that when there is not a value defined by the user to be assigned, the "empty" value corresponding to the %1 attribute data type will be used.

rgz0008

Attribute %1 changed from AllowNulls=Yes to AllowNulls=No and no initial value was specified. Null values will be treated as empty ones.

When changing the value of the AllowNulls property of the %1 attribute from Yes to No, the reorganization process can find records with the %1 null value. 

The message indicates that if, during the reorganization process, null values are found for the %1 attribute, they will be substituted by the "empty" value corresponding to the %1 attribute data type.

rgz0009

AutoNumber=True ignored. Attribute %1 is not table %2 primary key.

The Autonumber property applies only when the attribute is the primary key of a table. It does not apply when it is part of a primary key (made up with more attributes). 

The message indicates that the primary key of the %2 table is made up with other attributes (in addition to the %1 attribute) or that the %1 attribute is not part of the 2 %table key.

rgz0010

AutoNumber=True ignored for attribute %1. Autonumbering is not supported in this DBMS.

The %1 attribute should be defined as auto-numbered in the table that is being created/reorganized, but the DBMS for which it is being generated does not support the AutoNumber property.

rgz0011

Secondary attribute %1 in more than one table.

This error indicates that the %1 secondary attribute is stored in more than one table. This situation usually occurs when there are transactions that have not been defined yet in Design, or when the defined transactions "contradict each other".

rgz0012

%1 is associated to External file %2. It will not be reorganized.

In this model, the %1 table to be reorganized is associated to a Data view (%2) and this is the reason why it is not reorganized.

rgz0013

%1 is a table on the server and the Model property ''Reorganize Server tables'' is No.

The %1 table to be reorganized is not a local table and it has been required that only local tables should be reorganized.

rgz0014

Index name %1exceeds maximum name length allowed by language (%2 characters).

The selected programming language or DBMS cannot generate correctly with index names with more than %2 characters. The solution is to rename the index, change the programming language or DBMS, or change the method to access data.

rgz0015

Reorganization may fail if table %1 has records. Reference (%2) does not allow nulls and referenced table %3 is new (empty).

An integrity restriction, that cannot be null, has been created between table %1 and table %2,  which is new (without records). If table %1 has records the reorganization will fail.

rgz0016

Data lost may occur as duplicate key may arise when adding records to table %1 from multiple source tables (%2).

It occurs in reorganizations using several tables as data source to create a new table. It indicates that the records of the tables specified in %2 can have common key values and that, if this happens, duplicated secondary attributes data could be lost.

rgz0017

At lease one attribute in foreign key %2 does not have a (valid) "Initial value". Attribute %1 initial value ignored.

The message indicates that the value of the "Initial value" property must have been ignored since, otherwise, there is the possibility that the reorganization gets cancelled if the table that is being reorganized has records. The reason for the cancellation would be that there are records in the table to be reorganized that make reference to a foreign key (non-null) that does not exist in the table referred to. 

If you want that all the records of the table to be reorganized have a specific value (non-null) for the foreign key, you may carry out one of the following steps:  

a. Process completely carried out with GeneXus

§          Cancel the reorganization process. 

§          Add a valid value for"Initial value" to all attributes indicated as %2.

§          Verify that there is a record in the table referred to whose key coincides with the initial values given to the foreign key.

§          Reorganize the database.

b. Process carried out combining GeneXus with the DBMS tools

§          Continue the reorganization

§          Using the tools of the DBMS you are working with:

o      Verify that there is a record in the table referred to whose key coincides with the initial values desired for the foreign key.

o      Substitute the value of the attributes in the table that is being reorganized by the desired values.

rgz0018

Foreign key to new (empty) table %2 cannot be initialized. Attribute %1 initial value ignored.

The message indicates that the value of the "Initial value" property must have been ignored since, otherwise, there is the possibility that the reorganization gets cancelled if the table being reorganized has records. The reason for the cancellation would be that there are records in the table to be reorganized that make a reference to a foreign key (non-null) that does not exist in the table indicated as %2.  

If you want that all the records of the table to be reorganized have a specific value (non-null) for the foreign key, you may carry out one of the following steps:

a. Process completely carried out with GeneXus

§          Cancel the reorganization process. 

§          Delete the objects that define the table indicated as %2.

§          Reorganize the database.

§          Add the objects that define the table indicated as %2.

§          Reorganize the database again.

b. Process carried out combining GeneXus and the DBMS tools

§          Continue with the reorganization.

§          Using the tools of the DBMS you are working with:

o      Add a record with the desired key values in the table indicated in %2.

o      Substitute the value of the attributes in the table that is being reorganized by the desired values.

rgz0019

Reorganization may fail if table has records. Unique indexes should not be created on new attributes only.

A unique index is being created, which is made up only by new attributes (all of them with the same value). If the table has records, the reorganization will fail.

rgz0020

Reorganization may fail if there are duplicate values for %1.

A unique index is being created in the table. If the existing records have duplicated values, the reorganization may fail.

rgz0021

Unique index %1 on table %2 is not supported in this environment. Ignored.

If the environment does not support candidate keys, the unique indexes %1 of table %2 are ignored.

rgz0022

%1's data type (%2) is not supported on the selected environment (DBMS/Generator).

The attribute identified by %1 is %2 data type. The %2 data type is not supported by the DBMS and/or the combination DBMS/Generator. An alternative solution is changing the %1 attribute data type to one supported by the combination DBMS/Generator. Another alternative is changing the reorganization generator.

rgz0023

Attribute '%1' cannot have the same name of a table when it has the Autonumber property set on and using Oracle.

This message indicates that there is a table with the same name of an attribute that has the Autonumber property in ‘Yes’. In Oracle, this situation generates a names conflict that does not allow continuing the reorganization. 

To support the Autonumber property, GeneXus creates a Sequence type object in Oracle. The name that GeneXus gives to this object is the name of the attribute that has the Autonumber property in Yes. Oracle does not support that a table and a Sequence object have the same name. 

Solution: modifying the name of the attribute or of the table to avoid the conflict.

rgz0024

Column count of index %1 exceeds maximum allowed by DBMS (%2).

The amount of columns of index %1 exceeds the maximum supported by the DBMS. This maximum value is indicated in %2.

It is necessary to reduce the amount of column for this index to solve the problem.

rgz0025

Initial value %1 for attribute %2 does not have the correct Data Type or is out of range.

The value %1 of the Initial value property for attribute %2 does not match attribute's data type or is out of range. The Initial value property value must be:

§          A string delimited with single or double quotes for Character, Varchar or Long Varchar attributes. For example: "My initial value" or 'My initial value'.

§          A numeric value for numeric attributes. For example: 1234, 1.23, -10.

§          A date value in YYYY-MM-DD format for Date attributes.

§          A DateTime value in YYYY-MM-DD HH-MI-SS format for DateTime attributes.

rgz0028

Datatype, length or decimal places of %1 are not valid for an autonumbered attribute.

Attributes with the Autonumber property set must be Numeric without Decimal places and when Access is the DBMS the length should be between 5 and 9.

rgz0029

Reorganization may fail if table %1 has records and the key value %2 does not exist in table %3.

A new not null referential integrity constraint has been created from table %1 to table %3. If table %1 has records and the value for the referenced key (%2) does not exist in table %3, the reorganization will fail.