This is actually a repost question that was already answered under the forum subsection for navision >=3.7 but I need to rephrase to apply for 3.6 version.
http://www.mibuso.com/forum/viewtopic.p ... m+tracking
Are there any issues or restrictions (or lack of required functionalties) with Navision
3.6 that will need to be considered for Navision 3.6/Item tracking module with respect to capturing bar code and lot numbers? The above post mentioned some bugs with 3.6 in the navision/item tracking module - are there not any navision patches to deal with these bugs? (as an alternative to upgrading the whole navision to 3.7).
And for some reason, we are being led to believe the sql server option for navision is criticial for versions >=3.6 . Any rationality behind this?
Any suggestions on this are greatly appreciated.
Thank you.
Ali.
Comments
Both databases (Native or SQL) are still viable options up through and including the current 4.0 release (and maybe beyond). Which database you select is dependent on your requirements.
There are pros and cons of both databases and your decision should be based on your needs instead of software limitations.
In a nutshell, Navision database requires less maintanence than SQL Server.
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