Sales History functions : Slow retreive data

S0918423470

Hello all,

In Nav 4.0 Sp3, I used Invoice form and i chose the Sales History func to open Form Customer History. It's so slow to load the data, i see the dialog

Searching the Sales Invoice Line table :

Counter : 1 901 888
Table : Sales Invoice Line
Key : Document No, Type, Line No.

How can i do to improve the speed of seraching???
I checked related objects (from F7171 ->7176), but i did not see this key used.
Maybe, i expand data to have more spaces ?? I have 30% free database, it's ok or should be more than??

I read the Application User Guide about the key and indexes.
I found that :

The overall speed of C/SIDE depends on a number of factors:
· The size of your database
· The number of active keys
· The complexity of the keys
· The number of records in your tables
· The speed of your computer and its disk system

How can i speed my retrieving??
](*,) ](*,) ](*,) [-o< [-o<
Thanks,
HN

Mbad

Arent you filtering on customer? If so use a key that includes customer no.

nunomaia

Key Document No, Type, Line No. It's the default if you don't select any.
If you are using any filter, than check if is necessary to add a key.

S0918423470

Hi,

It's standard form of NAV 4.0, i do nothing about the filter. I only uses it :x .

With table 113 Sales Invoice Line : Document No, Line No is the primary key, after the system uses indexes, they continue with this.

Maybe, the Navision Native Database, the data manager is not good???
The indexes not work well?? As i know the indexes to help the searching faster and faster.
But it seems that , the large database and huge records make the indexes effection so bad ????

I don't know which is the good reason to explain this.
Any body help me pls, i need some advices for this case.

Thanks,
HN

Mbad

S0918423470 wrote:

Maybe, the Navision Native Database, the data manager is not good???
The indexes not work well?? As i know the indexes to help the searching faster and faster.
But it seems that , the large database and huge records make the indexes effection so bad ????

1. Nothing wrong with the dbms
2. Indexes on native work well
3. Large databases work like large databases work. Nothing specificly wrong with native.

Your choice of keys always make all the difference.
2.000.000 will always take a while to go through.

Did you rememeber to call?
CustSalesHistory.SETRECORD(Cust);
CustSalesHistory.LOOKUPMODE := TRUE;
CustSalesHistory.RUNMODAL;

But you are somewhat right. Navigation pane should never have been made!