This is from MBS - I received it via my company's internal Tech Support:
Note: To upgrade to Microsoft Dynamics NAV 2009 SP1 from Microsoft Dynamics NAV 2009 or any previous version, you must perform a full upgrade of all files and objects to ensure they are compatible with the Microsoft Dynamics NAV 2009 SP1 platform. You must also update Web services. For information on how to upgrade, see the Upgrade Toolkit included in the product download, the Developer’s Toolkit for Microsoft Dynamics NAV, and the Developer and IT Pro Help on MSDN.
Can anyone verify / reject the above statement? I can understand the above if speaking RTC only, but not the classic (native / SQL) client...
Chris Studebaker
0
Comments
I have upgraded one client from 5.0 to 2009 executable.
I have upgraded a client on 4.0 with Lanham E-ship to 2009 exe for sole purpose to use webservices. 2 weeks ago we went live with their website integration through web services.
They also have RTC running but only for the purpose of website integration to do testing of entering orders/ debugging issues.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Yes, this statement is true ONLY for RTC only, not the classic client.
For NAV2009 RTC, you cannot simply just upgrade the executables or else you'll get a bunch of garbage on the RTC.
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
Is it only for RTC? Is this something you received directly from MS?
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Start off with NAV2009 installation with the database. Then upgrade your executable to NAV2009 SP1. Start the RTC and you'll get garbage.
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
I don't think they ever publicly supported executable upgrades.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Like I said, if you're using RTC, you have to do a full upgrade from NAV2009 to NAV2009 SP1. Or else your RTC pages will not display properly.
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
RIS Plus, LLC
Min thing when doing upgrade from NAV2009 to SP1 is that you need to recompile all objects after the upgrade and some pages must be "redesigned" to work correctly, because many things have changed...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
You cannot expect the Code Base in a ..NAV2009 Database to work fully functional with NAV 2009 SP1 RTC or Web Services. Obviously the versions before NAV2009 will not have pages, but even a uncustomized NAV2009 database will not be fully functional with NAV 2009 SP1 Executables.
For example: Try the Setup Automatic include Exstended Texts for an Item in a NAV 2009 Database using NAV2009 SP1 RTC executables and then go and create a SO for the Item...
OR try a Web Service with a COMMIT statement in it and the line after an ERROR, test it with NAV2009 and NAV 2009 SP1 exe's you'll see the differance.
For a pure Classic Implementation I am not aware of any direct issues as such,nevertheless it is not supported.
And I just tested it in 2009 SP1, and it executes COMMIT so if you have commits in your code, you'll be left with inconsistent data.
I wish they left that as an option to enable or disable in code that is being published.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Couldn't agree more =D>