Four Js Development Tools Forum

Discussions by product => Genero BDL => Topic started by: David H. on April 29, 2009, 11:51:49 am


Title: Error 2029 compiling a form with Genero v2.11.xx
Post by: David H. on April 29, 2009, 11:51:49 am
When the attached form is compiled with Genero v2.11.02-v2.11.14 we get an error 2029. When compiled with Genero v1.32 it compiles fine....


Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: Sebastien F. on April 29, 2009, 12:03:33 pm
Hello,
Can you provide the database schema file please?
Seb

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: David H. on April 29, 2009, 12:17:20 pm
Hi Seb.

Please see attached. Hope there is nothing wrong with the schema as I wrote my own function to generate schema's automatically whenever a change in our database structure is detected!

Cheers.

David

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: Sebastien F. on April 29, 2009, 12:24:17 pm
Thanks David,

Actually you have some fields like a2, a5, a8 that are defined with the (old) multi-line field tag, repeating the tag name in each line:

Code
  1. UNLOAD[a2                                                                    ]
  2. REMARK[ a2                                                                   ]
  3.       [ a2                                                                   ]
  4.       [ a2                                                                   ]
  5.       [ a2                                                                   ]
  6.  

This is now interpreted as a list/Matrix field...

You should remove the tag name in subsequent tags.

Seb

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: Sebastien F. on April 29, 2009, 12:26:01 pm
Sorry little typo in per example, you have actually:

Code
  1. UNLOAD[a2                                                                    ]
  2. REMARK[a2                                                                    ]
  3.       [a2                                                                    ]
  4.       [a2                                                                    ]
  5.       [a2                                                                    ]

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: David H. on April 29, 2009, 12:48:29 pm
Cheers for that. The error message sent me looking in the wrong direction totally!

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: Sebastien F. on April 29, 2009, 03:21:03 pm
Hum... yes...

I wonder why we don't have the same error message as Informix form4gl:

Code
  1. DATABASE FORMONLY
  2. SCREEN
  3. {
  4. [f1        ]  [f2                  ]
  5. [f1        ]  [f2                  ]
  6. [f1        ]
  7. }
  8. END
  9. ATTRIBUTES
  10. f1 = FORMONLY.field1;
  11. f2 = FORMONLY.field2;
  12. END
  13. INSTRUCTIONS
  14. SCREEN RECORD sr[5](FORMONLY.*);
  15. #
  16. #      Screen record array "sr" has component sizes which either
  17. # differ from the specified dimension of the array or differ among themselves.
  18. # See error number -2029.
  19. END
  20.  

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: Reuben B. on April 29, 2009, 11:01:10 pm
This page in the documentation has a description for each each error message and a suggested solution.  https://4js.com/techdocs/genero/fgl/devel/DocRoot/User/FglErrors.html

Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: David H. on April 30, 2009, 04:16:48 pm
Quote from: Reuben Barclay on April 29, 2009, 11:01:10 pm
This page in the documentation has a description for each each error message and a suggested solution.  https://4js.com/techdocs/genero/fgl/devel/DocRoot/User/FglErrors.html

Hi Reuben,

Believe it or nor I did actually check there before posting but the way the error was presented:-

 
Code
  1.   SCREEN RECORD arrdisc_srec (
  2. # Screen record array 'arrdisc_srec' has different component sizes.
  3. # See error number -2029.
  4.                                    unload_complete,
  5.                                    unload_date,
  6.                                    unload_text,
  7.                                    gross_wt,
  8.                                    new_gross_wt,
  9.                                    wt_text,
  10.                                    deprt_tran_id,
  11.                                    new_deprt_trans,
  12.                                    deprt_text,
  13.                                    deprt_tran_ntnlity,
  14.                                    new_ntnlity,
  15.                                    ntnlity_text,
  16.                                    msg_mrn
  17.                                    ,
  18.                                    no_packages,
  19.                                    new_no_packages,
  20.                                    packages_text,
  21.                                    no_items,
  22.                                    new_no_items,
  23.                                    items_text
  24.                                    ,
  25.                                    ncts_dclrn_type,
  26.                                    cwcx_key,
  27.                                    dest_coun_key,
  28.                                    cont_ind,
  29.                                    declarer_name,
  30.                                    consignor_name,
  31.                                    consignee_name,
  32.                                    deprt_cstm_off_key
  33.  
  34.                                )
  35.  

Made me think the error was within the screen record itself and not something wrong within the screen section. I think I must have been having one of those days! :-)