SRC Messages

Official Content
This documentation is valid for:

SRC is an abbreviation of the source term. The following list shows the error messages related to the GeneXus source, that can appear in the Output window when you try to save an object.

Code Message
 
src0020 Line is too long.
  This message informs you that the length of a code line is longer than allowed.
 
src0206 '%1' command is out of scope.
  This message informs you that a certain command is being used inside an object or section that it is not allowed.
 
src0213 '%1' invalid date constant; expected format: #YYYY-MM-DD HH:MM:SS.SSS#
  This message is displayed when you assemble several values to make up a date but the format is incorrect.
 
src0227 Conflict between %1 Function and Object Name.
  This warning message is displayed when an object in the KB has the same name as a function. For example, GeneXus offers the Color function, so, if an object has the de same name, this error will be displayed. To avoid this warning, you have to rename the object so that the conflict disappears.
 
src0246 Call to non-defined object '%1'
  Informational message displayed when the object '%1' is an external program (look at Call command for additional information); an external program is not modeled inside the Knowledge Base, you must provide its implementation or a compilation error will be found.

Note: FTP Functions are modeled as external programs (they are not a GeneXus standard function even when the standard classes can provide its implementation).
 
src0274 Last parameter cannot be omitted.
  This message is displayed when you are applying a method to an object, variable, etc., the method accepts optional parameters, and you have left a comma before the final parenthesis.
The last parameter you decide to specify must be followed by the final parenthesis. On the other hand, if you specify something like &var.method(par1,) or &var.method(par1,,,,) this message will be displayed as an error or warning depending on the case.
If you don't want to specify an optional parameter in the middle, you can define &var.method(par1,,par3) but if you don't want to specify some last optional parameters, you only have to omit them.
 
src0287 Program %1 does not exist.
  This message is displayed when you invoke an object that not exists in the KB.
 
src0294 Uknown function %1.
  This message is displayed when you invoke an object that returns a value and the object is not defined in the KB.
 
src0297 Variables cannot be used in formulas.
  This message is displayed when you use a variable in a formula. Remember that Variables are local and formulas are global. Ref.: Global Formulas
 
src0299 Wrong number parameters: %1 expects at least %2 parameters.
  This message is displayed when a GeneXus function -like 'addyr'- requires a different number of parameters than the declared.
 
src0306 %1 subroutine is defined but never used.
  This message notifies that an object has a subroutine defined but not called.
 
src0310 %1 is not a transaction or transaction level.
  This message notifies that the name referenced as a Base Transaction next to a For each command is incorrect because a Transaction does not exist with that name nor a TransactionName.LevelName.
 
src0311 Conflict between %1 rule and Object Name.
  This warning message is displayed when an object in the KB has the same name as a rule. For example, GeneXus offers the Order rule, so, if an object has the de same name, this error will be displayed. To avoid this warning, you have to rename the object so that the conflict disappears.
 
src0312 '%1' command is out of scope. It is not guaranteed to work.
  This message informs you that a certain command is being used inside an object or section that it is not allowed.

See also