Hi

Its not table Maps that are slow but this particular method that has a problem. 
You need to focus on optimising the method and the methods that it calls. I'm 
guessing that you have a problem with this statement due to the large number of 
customer/vendor transactions that you have and that you could go some way to 
solving the problem by providing a covering index on table custSettlement & 
vendSettlement tables to support the select executed in the CustTrans/VendTrans 
transactionPerDate method (i.e. make that method run as fast as possible and 
you'll have a done the same to the Map method.

Regards


Malcolm Burtt
Touchstone
People, Partnerships, Solutions


From: development-axapta@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of 
thnathan
Sent: 06 November 2007 13:56
To: development-axapta@yahoogroups.com
Subject: [development-axapta] Map performance


AX 3.0 SP2
\Data Dictionary\Maps\CustVendTable\Methods\balancePerDate
This statement is seriously slow.
Any ideas on improving maps?



[Non-text portions of this message have been removed]

Reply via email to