Forms Statement Error Number 1340
Invalid year in date. -1205 Invalid month in date. -1206 Invalid day in date. -1207 Converted value does not fit into the allotted space. -1208 4gl error codes There is no conversion from non-character values to character values. -1209 Without any delimiters, informix sql error codes this date must contain exactly 6 or 8 digits. -1210 Date could not be converted to month/day/year format. -1211 Out of informix error memory. -1212 Date conversion format must contain a month, day, and year component. -1213 A character to numeric conversion process failed. -1214 Value too large to fit in a SMALLINT. -1215 Value too large to fit in an INTEGER. -1216 Illegal exponent. -1217 The format string is too large. -1218 String to date conversion error. -1219 Numeric value from database is too large for COBOL data item. -1220 Numeric value from database is too small for COBOL data item. -1221 Cannot convert null data types. -1222 Value will not fit in a SMALLFLOAT. -1223 Value will not fit in a FLOAT. -1224 Invalid decimal number. -1225 Column does not admit a NULL value. -1226 Decimal or money value exceeds maximum precision. -1227 Message file not found. -1228 Message number not found in message file. -1229 Incompatible message file. -1230 Bad message file name formulation. -1231 Cannot seek within message file. -1232 Message buffer too small. -1233 Invalid hour, minute, or second. -1234 Function may be applied only to datetime data types. -1235 Character host variable is too short for the data. -1236 Bad era date. -1237 Bad era name. -1238 Bad era initialization. -1239 Era year overflow. -1250 Unable to create pipes. -1251 Unable to create shared memory. semget failed. -1252 Unable to create shared memory. shmget failed. -1254 Unable to connect to remote host. -1257 Operating system cannot fork process for back end. -1258 Cannot attach to shared memory used to communicate with back end. -1260 It is not possible to convert between the specified types. -1261 Too many digits in the first field of datetime or interval. -1262 Non-numeric character in datetime or interval. -1263 A field in a datetime or interval is out of range or incorrect. -1264 Extra characters at the end of a datetime or interval. -1265 Overflow occurred on a datetime or interval operation. -1266 Intervals
(0) Histórico http://informix-technology.blogspot.com/2012/02/4gl-whenever-error.html da Página Restrições Info Resolved comments Link para esta página… Exibir em hierarquia View Source Exportar para Word Linha Logix … error codes Linha Logix Home Base de Conhecimento Framework Administração Logix LFRW0001 - FORMS statement error number -1340 The error log has not been started. Ir para o forms statement error final dos metadados Created by Marlon Acacio Pinheiro, last modified on 04 mar, 2016 Ir para o início dos metadados Error: You are trying to view a page which does not yet have a published version available and you do not have permission to view draft versions. base_de_conhecimento versao_12 frw lg_frame_sup log6000 log00086 -1340 Powered by Atlassian Confluence 5.7.5, Team Collaboration Software Impresso por Atlassian Confluence 5.7.5, the Enterprise Wiki. Reportar um problema Notícias da Atlassian Atlassian
artigo está escrito em Inglês e Português English version: I believe this is the first time I cover a 4GL topic here. But a recent customer situation motivated me to write this. Hopefully most of the readers will just say "Yeah... Everybody knows that...", but it's not the first time I see people making the confusion I'm going to describe, and in my opinion that happens because it's not intuitive. Although it's perfectly documented, I suppose many people just follow the intuitive approach and fall into the problem. I'm talking about the WHENEVER statement. It is used to define the behavior of the program when(ever) a defined condition (ERROR, SQLERROR, WARNING, SQLWARNING or NOTFOUND) happens. The behavior can be CONTINUE, STOP, GOTO or CALL function. Seems pretty simple and handy... so why am I writing this? The usual confusion relates to the scope of the WHENEVER statement. At first glance you could think this was a program instruction, and the effect or scope of it would be until the program flow reached another WHENEVER statement. And this is the confusion many people make. In reality it's not a program instruction, but instead it's a compiler directive. As stated in the documentation the scope is local to the module where it appears. If the module contains only function definitions, then all this functions will behave accordingly to the conditions used in the WHENEVER statement. The program flow is irrelevant. This is better shown with a practical example (line numbers added for clarity) 1 DATABASE sysmaster 2 MAIN 3 DEFINE v INTEGER 4 CALL func_1() RETURNING v 5 END MAIN 6 7 FUNCTION func_0() 8 WHENEVER ERROR CONTINUE 9 END FUNCTION 10 11 FUNCTION func_1() 12 SELECT no_column FROM no_table 13 RETURN 1,2 14 END FUNCTION Ok, this is a very simple 4GL program that uses sysmaster database. It has two functions: func_0 Is never called, but contains a WHENEVER ERROR CONTINUE which tells 4GL to continue execution when it encounters an error func_1 This contains two errors. It tries to access a table that doesn't exist and returns two values (and the CALL on line 4 expect only one) If we compile and execute it we get: cheetah@pacman.onlinedomus.net:fnunes-> c4gl -o test.4ge test.4gl;./test.4ge Program stopped at "test.4gl", line number 4. FORMS statement error number -1320. A function has not returned the correct number of values expected by the ca