this is the so called "48 feature" it doesn't have anything to do directly
with localmacros or containers.
you'll get the same internal compiler overflow "hey what are you doing"
using update_recordset command with more than 48 fields to set.
in this case you have NO chance beside "duplicating" the update_recordset
call setting the next fields.
btw: does anyone have reported this already (and have got an usable answer)
?????
regards
Douglas
----- Original Message -----
From: "Sonny Wibawa Adi" <[EMAIL PROTECTED]>
To: <Axapta-Knowledge-Village@yahoogroups.com>
Sent: Friday, July 08, 2005 11:09 AM
Subject: Re: [Axapta-Knowledge-Village] Localmacro help please
> Hi, Hennie Potgieter,
>
>
> Axapta has a stack memory limitation for total
> elements in a container. You may solve this problem by
> reducing the total elements in a container by dividing
> them into containers.
> I tried to create a container and as I know, the
> maximum element is 48.
>
> You can change the macro in classDeclaration, pack and
> unpack method:
>
> //classdeclaration
> class MyReport extends RunBaseReport
> {
> #localmacro.CurrentList1
> a1,
> a2,
> //... 48 elements
> a48
> #endmacro
> #localmacro.CurrentList2
> b1,
> b2,
> //... 48 elements
> b48
> #endmacro
> #localmacro.CurrentList3
> c1,
> c2,
> //... 48 elements
> c48
> #endmacro
> }
>
> public container pack()
> {
> return [#CurrentVersion,
> [#CurrentList1],
> [#CurrentList2],
> [#CurrentList3],
> super()];
> }
>
> public boolean unpack(container packedClass)
> {
> int version =
> runbase::getVersion(packedClass);
> Container con;
> Container con1;
> Container con2;
> Container con3;
>
> switch (version)
> {
> case #CurrentVersion:
> [version,con1,con2,con3,con] =
> packedClass;
> [#CurrentList1] = con1;
> [#CurrentList2] = con2;
> [#CurrentList3] = con3;
> return super(con);
> default :
> return false;
> }
>
> return false;
> }
>
> Good luck!
>
> Regards,
>
> Sonny Wibawa Adi, MBCSP, MCAD.NET, MCSD.NET, MCP
>
>
> --- Hennie Potgieter <[EMAIL PROTECTED]> wrote:
>
>> Hi all,
>>
>> When a localmacro list object is defined in the
>> classDeclaration, only a
>> certain number of variables are allowed. The pack
>> and unpack methods
>> gives the following compiler error: "Overflow in an
>> internal compiler
>> stack."
>>
>> #LOCALMACRO.ParmList
>> parmId,
>> .
>> .
>> //variable list of 108 variables
>> #ENDMACRO
>>
>> Is this an Axapta problem? Should more than 1
>> localmacro list object be
>> used? How would more than 1 localmacro list object
>> be implemented?
>>
>> -*
>> Hennie Potgieter
>> Senior Business Analyst
>> UTi SUN Couriers Division
>> Centurion, South Africa
>> Cell: 0829208315
>> mailto: <mailto:[EMAIL PROTECTED]>
>> [EMAIL PROTECTED]
>>
>>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> Sharing the knowledge on Axapta.
> Yahoo! Groups Links
>
>
>
>
>
>
Sharing the knowledge on Axapta.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
