Hi! I read on this forum that it’s possible to update the executables of previous version of Navision to the latest version of Attain. [:p] What kind of emprovement can give that? Better performances? I think that the ODBC interface must be upgraded too. Am i right? Can anyone show the correct procedure? Thanks in advance. [:D]
It certainly depends on what version you’re thinking of upgrading from, what server you’re using, etc. But in general you’re right. You’ll get better performances, a more stabile product and all the new C/SIDE - C/AL features and functions to use in your custom programming.
Be aware however, that you can encounter strange behaviour in some application areas. E.g the shell command works differently in version 3.6 than it did in previous versions (it doesn’t work like it should), thus you might get unexpected results, say when using 2.6 code with shell calls with the 3.6 executable. Also dataports have undergone some changes which could lead to unexpected results.
Ok. Thank you all. I am porting a manufacturing 2.01 to the Attain 3.60 sql server option, and it’s terrific! Meantime, it’s necessary to compress warehouse entries, but there are about 3g of data and it’s a very slow process… Upgrading executables from 2.01 to 3.60 is a great jump…maybe it’s better to wait 'til the end of the complete porting, insn’t it?
Actually domenico, if you are upgrading, then the executables should be the first step.
Yes… i mean, while i’m porting all the customizations (about 722 objects changed in 2.01), do you suggest me to use 3.60 (or 3.70) executables with 2.01 manufaturing database? Thanks
First step in an upgrade is to get the existing objects running on the latest executables. The recommended procedure is to backup your xisting (2.01) system, and restore it into a brand new 3.60 Database. (Don’t work with 3.60 it has too many problems).
Ok, thanks you all. After this “bath of blood” due to a complete migration from 2.01 to 3.70, i’ll keep up-to-date the executables to next version. [xx(] Bye.