When drilling down navision gets slow or not responding. I have tried with file → database → Information → Tables → optimize. Even after this iptimization it takes long.
What should I do with this? Is it regular to have this slow process? [:S]
OK, in this case my first receommendation is: DO NOT USE THE NAV-TABLE OPTIMIZER!
This feature really sucks [:@], and all it does (Index rebuild, SIFT Maintenance) could be accomplished much smarter.
With NAV 5.0 (without SP1) you have to look into SIFT Optimization; e.g. reducing the number of “Buckets” (leaving only the pre-last one), in firts place. Also, SIFT Mainetenance is crucial (see http://www.mibuso.com/dlinfo.asp?FileID=812)
First, Scrollbar is very “special” in Navision forms [:@]
I was told years ago better not to touch it at all - look at its behaviour, it’s not normal Windows scrollbar, from which you can tell approx amount of lines… It changes in lenght following uncertain pattern, then, if you move it down when it is small, it starts to scroll, then suddenly scrolling stops and it jumps back, nothing happens for some time, even no “hourglass” cursor - then “Not responding” appears. If you have enough patience, after some time suddenly list jumps, form becomes responsive again, but you can’t get any idea how far it jumped and exactly in what position in long list you are now.
Use PgUp - PgDown, and better, apply some filtering to eliminate row count. Scrolling through list of half-million lines is bad idea. Don’t put FlowFields in such list - otherwise if you’ll press Ctrl-End being on first row, Navision will retrieve all data over network, calculate all FlowFields, and THAT takes time, this job is performed on workstation by Navision client, no DB optimisations or monsterous server hardware can help here.
Until MS would not get rid of Native database and rewrite Navision to use SQL server huge possibilities at full blow, there will be problems, although even now things get better with each version or even SP - as it was with 5 and 5 SP1. But MS is still enforced to mimicrize FlowFields on SQL server, to maintain compatibility with Native database.