4D v16.3

Syntax Errors (1 -> 81)

Home

 
4D v16.3
Syntax Errors (1 -> 81)

Syntax Errors (1 -> 81)  


 

 

The following table lists the syntax error codes for errors that may occur during code execution in the Design or Application environment. Some of these errors may occur in interpreted mode only, some in compiled mode only, some in both modes. You can intercept these errors using an error interruption method installed using ON ERR CALL.

CodeDescription
1A “(” was expected.
2A field was expected.
3The command may be executed only on a field in a subtable.
4Parameters in the list must all be of the same type.
5There is no table to which to apply the command.
6The command may only be executed on a Subtable type field.
7A Numeric argument was expected.
8An Alphanumeric argument was expected.
9The result of a conditional test was expected.
10The command cannot be applied to this field type.
11The command cannot be applied between two conditional tests.
12The command cannot be applied between two Numeric arguments.
13The command cannot be applied between two Alphanumeric arguments.
14The command cannot be applied between two Date arguments.
15The operation is not compatible with the two arguments.
16The field has no relation.
17A table was expected.
18Field types are incompatible.
19The field is not indexed.
20An “=” was expected.
21The method does not exist.
22The fields must belong to the same table or subtable for a sort or graph.
23A “<” or “>” was expected.
24A “;” was expected.
25There are too many fields for a sort.
26The field type cannot be Text, Picture, Blob or Subtable.
27The field must be prefixed by the name of its table.
28The field type must be Numeric.
29The value must be 1 or 0.
30A variable was expected.
31There is no menu bar with this number.
32A date was expected.
33Unimplemented command or function.
34Accounting files are not open.
35The sets are from different tables.
36Invalid table name.
37A “:=” was expected.
38This is a function, not a procedure.
39The set does not exist.
40This is a procedure, not a function.
41A variable or field belonging to a subtable was expected.
42The record cannot be pushed onto the stack.
43The function cannot be found.
44The method cannot be found.
45Field or variable expected.
46A Numeric or Alphanumeric argument was expected.
47The field type must be Alphanumeric.
48Syntax error.
49This operator cannot be used here.
50These operators cannot be used together.
51Module not implemented.
52An array was expected.
53Indice out of range.
54Argument types are incompatible.
55A Boolean argument was expected.
56Field, variable, or table expected.
57An operator was expected.
58A “)” was expected.
59This kind of argument was not expected here.
60A parameter or a local variable cannot be used in an EXECUTE statement in a compiled database.
61The type of an array cannot be modified in a compiled database.
62The command cannot be applied to a subtable.
63The field is not indexed.
64A picture field or variable was expected.
65The value should contain 4 characters.
66The value should not contain more than 3 characters.
67This command cannot be executed on 4D Server.
68A list was expected.
69An external window reference was expected.
70The command cannot be applied between two Picture arguments.
71The SET PRINT MARKER command can only be called in the header of a form being printed.
72A pointer array was expected.
73A numeric array was expected.
74The size of arrays does not match.
75No pointer on local arrays.
76Bad array type.
77Bad variable name.
78Invalid sort parameter.
79This command cannot be executed during the draw of a list.
80Too many query arguments.
81The form was not found.

Tips  

Some of these error codes denote plain syntax errors due to mistyping. For example, you get an error #37 if you execute the statement v=0 when you actually meant v:=0. You can eliminate the error by fixing your code in the Method editor.

Some of these error codes are due to simple programming errors. For example, you get an error #5 if you execute an ADD RECORD command, when you have not first set the default table (using the DEFAULT TABLE command), and do not pass the table parameter. In this case, there is no table to which to apply the command. You eliminate the error by checking to see if you forgot to set the default table or if you forgot to pass the table parameter to the command for this occurrence.

Some of these error codes denote errors due to a flaw in the design. For example, you get an error #16 if you apply RELATE ONE to a field that is not related to any other field. You eliminate the error by checking to see if your code is actually wrong or if you simply forgot to create the relation starting from the field.

Some errors, when they occur, are not always located exactly where your code breaks. For example, if in a subroutine you get an error #53 (indice out of range) on the line vpFld:=Field($1;$2), the error is due to a wrong table and/or field number that has been passed to the subroutine as a parameter. Therefore, the error is located in the caller method and not where the error actually occurs. In this case, trace your code in the Debugger window to determine which line of code is the real culprit, then fix it in the Method editor.



See also 

ON ERR CALL

 
PROPERTIES 

Product: 4D
Theme: Error Codes

 
HISTORY 

 
ARTICLE USAGE

4D Language Reference ( 4D v16)
4D Language Reference ( 4D v16.1)
4D Language Reference ( 4D v16.2)
4D Language Reference ( 4D v16.3)