We are looking for some feedback on SP2. We are somewhat ‘shy’ after painful upgrade from v2.5 to v3.0 a few months ago. Any input would be appreciated. Regards from Vancouver, Canada Mark
Hi, Axatpa did the upgrade job well. We have upgraded a couple of customer systems into sp2. It was easier than we expected. Both systems had modifications, but we had to do only minor corrections into the code. At first we did a copy of the running system by duplicating everything (also the database and ODBC-connection) in order to rename the copy back to production if the upgrade does not work. There was some difficulties to upgrade the CRM-data model because of some duplicate entries and the batch job didn’t end normally. Afterwards we did a full synchronize in the administrator menu → SQL → etc. It pinpointed us those duplicates and after washing them out and running the job again the data is ok We did test conversions in the office and trained ourselfes to look out wise enough before going to customer’s site 
The real upgrade was fast, the systems were down less than two working days. The second morning was reserved for customer testing and after it we upgraded the clients. Problem: If you are running through AOS there is no problem. But when old 2-tier clients versions start the upgraded axapta it goes to upgrade mode! Perhaps trying to “upgrade” it back to sp1 
Solution: To avoid this, we renamed the share name of the applicacion directory from “axapp3” to “axapp32”. Now the users could not start axapta before client was upgraded and the configuration was corrected. It seems that now 3-tier clients run in a limited BW and high latency faster than before, thanks to cache corections.
Thanks very much for your input. I am now more encouraged about this. Regards, Mark