Urgh, that's pretty difficult...When you create the report design, Axapta reserves the space for all footers in design. Let's suppose 5 pagefooters, with a height of 10 mm. each, but you've programmed it to print only 3 of them. Well, when you print that report, even tough only 3 pagefooter
Dear Malcom and Vaibhav or anyone
else,
Can you tell me the detail of creating upgrade
project?
And where i find the compare tools and how to use
it?
Regards,
Joy
- Original Message -
From:
vaibhav
pednekar
To: Axapta-Knowledge-Village@yahoogroups.com
Hi
Joy
The upgrade
project is the mechanism used when you receive a new version from MBS (its
accessed from Tools - Development Tools - Version update), but on closer
inspection, its not the tool you want. You actually need to use the "Compare
layers" tool which can be found in the
Hi all
i had
created a purchase order with a item of quantity (suppose 100).suppose these 100
items belongs to three diffrent batches,how can ihandle these sitution so
that it sits accordingly to their batchid in inventory.the condition
is,i have to createonly a single linein
Dear all,
I have created a macro in the AOT containing the following:
#localmacro.TRA_Macro_Local1
print Hello local world;
pause;
#endmacro
Now I created a job containing the following:
static void TRA_Macro_Global1(Args _args)
{
#TRA_Macro_Local1
}
I expected I could just call
static void Jobx(Args
_args){#localmacro.TRA_Macro_Local1 print "Hello
local world"; pause;#endmacro
#TRA_Macro_Local1}
now
push F5 (execute)
Otto
-Ursprüngliche Nachricht-Von: Danny Gaethofs
[mailto:[EMAIL PROTECTED]Gesendet: Donnerstag, 23. Dezember 2004
14:51An:
Otto, you're defining a local macro:static void Jobx(Args _args) { #localmacro.TRA_Macro_Local1 print "Hello local world"; pause; #endmacro #TRA_Macro_Local1 } Danny wants to use a global one!! The right version would be:Macro Macro1 is listed:#define.salute1(print 'Hello World';
Hello Danny Gaethofs,
÷åòâåðã, 23 äåêàáðÿ 2004 ã., you wrote:
DG How can I put a large amount of code in a macro and execute it at
DG compile time?
just remove #localmacro and use AOT macro name instead:
\Jobs\Test_Macro:
static void Test_Macro(Args _args)
{
;
#TEST_MAcro
}
Thanks Raul, Max, Otto,
This confirms what I have been seeing.
You always have to declare the macro before you can use it.
There is not much difference between a macro library and a global
macro or a local macro defined in the AOT.
You have to declare it first before you can use it in a
Hi
all
I Need to create a
Job that is Going to Check the PurchCostprice from the Inventtablemodule against
the Weightedcostprice in the System and then if different Change the
Inventsum.postedvalue to be the true purchcostprice * the Posted
Qty
I have the following
but am losing
10 matches
Mail list logo