Four Js Development Tools Forum

Discussions by product => Genero BDL => Topic started by: David Heydon on April 29, 2009, 11:51:49 AM

Title: Error 2029 compiling a form with Genero v2.11.xx
Post by: David Heydon 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 FLAESCH 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 Heydon 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 FLAESCH 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 (per) Select
UNLOAD[a2                                                                    ]
REMARK[ a2                                                                   ]
      [ a2                                                                   ]
      [ a2                                                                   ]
      [ a2                                                                   ]


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 FLAESCH on April 29, 2009, 12:26:01 PM
Sorry little typo in per example, you have actually:

Code (per) Select
UNLOAD[a2                                                                    ]
REMARK[a2                                                                    ]
      [a2                                                                    ]
      [a2                                                                    ]
      [a2                                                                    ]
Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: David Heydon 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 FLAESCH 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 (per) Select

DATABASE FORMONLY
SCREEN
{
[f1        ]  [f2                  ]
[f1        ]  [f2                  ]
[f1        ]
}
END
ATTRIBUTES
f1 = FORMONLY.field1;
f2 = FORMONLY.field2;
END
INSTRUCTIONS
SCREEN RECORD sr[5](FORMONLY.*);
#
#      Screen record array "sr" has component sizes which either
# differ from the specified dimension of the array or differ among themselves.
# See error number -2029.
END
Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: 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
Title: Re: Error 2029 compiling a form with Genero v2.11.xx
Post by: David Heydon 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 (genero) Select
  SCREEN RECORD arrdisc_srec (
# Screen record array 'arrdisc_srec' has different component sizes.
# See error number -2029.
                                   unload_complete,
                                   unload_date,
                                   unload_text,
                                   gross_wt,
                                   new_gross_wt,
                                   wt_text,
                                   deprt_tran_id,
                                   new_deprt_trans,
                                   deprt_text,
                                   deprt_tran_ntnlity,
                                   new_ntnlity,
                                   ntnlity_text,
                                   msg_mrn
                                   ,
                                   no_packages,
                                   new_no_packages,
                                   packages_text,
                                   no_items,
                                   new_no_items,
                                   items_text
                                   ,
                                   ncts_dclrn_type,
                                   cwcx_key,
                                   dest_coun_key,
                                   cont_ind,
                                   declarer_name,
                                   consignor_name,
                                   consignee_name,
                                   deprt_cstm_off_key

                               )


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! :-)