The tables also optimizes if you make some change, then save & compile it.
This is NOT correct.
In case you change/create an index and comile&save it, this index will be optimized because it has been modified/created.
The prove for this : if you would save an object of a BIG table, saving it would cost a lot of time.
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Comments
http://www.BiloBeauty.com
http://www.autismspeaks.org
The tables also optimizes if you make some change, then save & compile it.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
In case you change/create an index and comile&save it, this index will be optimized because it has been modified/created.
The prove for this : if you would save an object of a BIG table, saving it would cost a lot of time.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!