4D v16.3

Erros de Sintaxe (1 -> 81)

Página Inicial

 
4D v16.3
Erros de Sintaxe (1 -> 81)

Erros de Sintaxe (1 -> 81)  


 

 

A tabela abaixo lista os códigos e as mensagens de erro de sintaxe que podem ocorrer durante a execução de código no ambiente Desenho ou Aplicação. Alguns destes erros podem ocorrer em modo interpretado apenas, alguns apenas em modo compilado e alguns em ambos modos. Pode interceptar esses erros usando um método de interrupção de erros instalado pelo comando  ON ERR CALL

CódigoDescrição
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.
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 Tipo must be Alphanumeric.
48Syntax error.
49This operator cannot be used here.
50These operators cannot be used together.
51Module not implemented.
52An Array was expected.
53Index 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 Tipo 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 paramater.
79This command cannot be executed during the draw of a list.
80Too many query arguments.
81The form was not found.

Dicas  

Alguns códigos de erro assinalam erros de digitação. Por exemplo, você obtém o erro  #37 se executar a expressão  v=0 quando na verdade queria escrever v:=0. Pode eliminar o erro corrigindo seu código no editor de métodos.

Alguns destes códigos de erro assinalam erros de programação simples. Por exemplo, você obtém o erro  #5 se executar um comando ALL RECORDS, sem indicar o nome da tabela no parâmetro correspondente, e ter definido a tabela padrão com a ajuda do comando DEFAULT TABLE. Neste caso, se corrige o erro definindo uma tabela padrão ou passando um nome de tabela no parâmetro correspondente.

Alguns destes códigos de erro assinalam erros relacionados com a estrutura do banco. Por exemplo, você obtém o erro #16 se aplica o comando RELATE ONE a um campo que não estiver relacionado com outro campo. Elimine o erro modificando seu código ou criando uma relação a partir do campo.

Certos erros nem sempre estão no lugar onde seu código parou. Por exemplo, se em uma subrotina você obtiver o erro #53 (index out of range) na linha vpCamp:=Campo($1;$2), o erro porque foi passado à subrotina como parâmetros números incorretos de tabelas ou de campos. Portanto, o erro está localizado no método chamador e não onde ocorre o erro. Neste caso, acompanhe seu código na janela do depurador para determinar que linha de código contém o erro, para corrigi-lo no editor de métodos.



Ver também 

ON ERR CALL

 
PROPRIEDADES 

Produto: 4D
Tema: Códigos de Erro

 
HISTÓRIA 

 
ARTICLE USAGE

Manual de linguagem 4D ( 4D v16)
Manual de linguagem 4D ( 4D v16.1)
Manual de linguagem 4D ( 4D v16.2)
Manual de linguagem 4D ( 4D v16.3)