mibuso.com
Home› Navision Attain

3.10 Database & Server with 4.0 SP3 runtime

DKNaviDKNavi Member Posts: 4
edited 2007-09-28 in Navision Attain
Hello O:)

I want to upgrade a customers 3.10 client & server to a 4.0 SP3 runtime. That means that the customers database will be a attain 3.10 and the client & server will be a 4.0 SP3.

Does anyone see a problem with that...

:?:
DKNavi

Comments

  • nunomaianunomaia Member Posts: 1,153
    No.

    It works fine. :)
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • krikikriki Member, Moderator Posts: 9,115
    I confirm that:no problem.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • viswanathviswanath Member Posts: 24
    no problem u can go for that
  • SavatageSavatage Member Posts: 7,142
    Are there any known Benefits to going to 4SP3 executables with a 3.10 database?
    Or are you doing it just because you can?
    Harry Ruiz
    http://www.BiloBeauty.com
    http://www.autismspeaks.org
  • nunomaianunomaia Member Posts: 1,153
    Savatage,

    I don't know if already used 3.10 executables, but stability it’s not its name.

    If a customer can make a technical upgrade some times will increase performance and solve other issues.

    By other hand time I have to admit it’s only because is "nice" to have the lasted version.
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • SavatageSavatage Member Posts: 7,142
    I'm sure that anyone who is using 3.10 is NOT still using 3.10 Executables.

    Probably most have moved to at least 3.7 executables.
    Assuming that is true:
    -I was wondering if anyone knew of any benefits from 3.7 to 4sp3 for a 3.10 database?
    Harry Ruiz
    http://www.BiloBeauty.com
    http://www.autismspeaks.org
  • David_SingletonDavid_Singleton Member Posts: 5,479
    Savatage wrote:
    I'm sure that anyone who is using 3.10 is NOT still using 3.10 Executables.

    Probably most have moved to at least 3.7 executables.
    Assuming that is true:
    -I was wondering if anyone knew of any benefits from 3.7 to 4sp3 for a 3.10 database?

    Yes that is a different question.

    I recently moved two companies to 4.00 SP2 executables. One from 3.10 the other from 3.70. The company on 3.10 noticed huge improvements, and it was very worth while. The company moving from 3.70 did not really se any great advantages. except the fix that correctly releases DB locks when a message is shown on a screen. But that one fix it self was enough reason to justify the move.

    When ever a company does any form of upgrade, it must always do an ROI to see if it is worth while. generally though as a rule of thumb, I recommend all clients to be no more than 2 versions behind on executables.

    The next thing, is that Navision has a long history, of "good" versions and "Bad" versions.
    0.9 good
    1.0 bad
    1.1 Good
    1.2 Bad
    1.3 good (last version of Navision with no bugs)
    1.4 aka 2.0 bad
    2.01 good
    2.5 bad bad bad bad
    2.6 good
    3.00 worse than bad could ever be
    3.01 bad
    3.10 good
    3.60 bad
    3.70 good
    4.00 bad
    4.00 sp1 bad
    4.00 sp2 good-native / bad SQL
    4.00 sp3 good both

    I break down 4.00 by service packs, because they really were different versions. Also note that the Good/Bad comment relates to the whole package, sometimes a bad comment is because of the EXE, somethign because of the DB.
    David Singleton
  • ara3nara3n Member Posts: 9,256
    Based on that trend. Nobody should upgrade to 5.:)
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • David_SingletonDavid_Singleton Member Posts: 5,479
    ara3n wrote:
    Based on that trend. Nobody should upgrade to 5.:)

    I am going to wait for 5.1 :mrgreen:
    David Singleton
  • SavatageSavatage Member Posts: 7,142
    great thoughtful info, David thanks.

    is your work in th NY area done yet?
    Harry Ruiz
    http://www.BiloBeauty.com
    http://www.autismspeaks.org
  • matteo_montanarimatteo_montanari Member Posts: 189
    DKNavi wrote:
    Hello O:)

    I want to upgrade a customers 3.10 client & server to a 4.0 SP3 runtime. That means that the customers database will be a attain 3.10 and the client & server will be a 4.0 SP3.

    Does anyone see a problem with that...

    :?:
    DKNavi

    We found some problems with last release:

    http://www.mibuso.com/forum/viewtopic.php?t=15328

    Eto
    Reno Sistemi Navision Developer
  • ara3nara3n Member Posts: 9,256
    Dty. I have not experienced any issue with sp3. I would test it.


    David

    I was at convergence and did ask 3 questions.

    1 Native Sift implementation on sql.
    They said they are working with sql guys.


    2 improved backup prosses
    On sql.
    Same answer.

    3 separate company in separate db.
    No plans to change it.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • yuppicideyuppicide Member Posts: 410
    We're still using 3.10 executables! :(

    Thanks for the information guys. It's good to know we can upgrade our clients if we want but still keep the server as 3.10. The company I work for is small, though, and won't pay for the upgrade so I'll have to live with 3.10a and it's flaws.
    Savatage wrote:
    I'm sure that anyone who is using 3.10 is NOT still using 3.10 Executables.

    Probably most have moved to at least 3.7 executables.
    Assuming that is true:
    -I was wondering if anyone knew of any benefits from 3.7 to 4sp3 for a 3.10 database?
  • nachoporcarnachoporcar Member Posts: 27
    I am also using 3.10 executables,

    my partner has not cleared up this. If I have undestand well i can use 3.70 or 4.0SP3 executables without migrating Navision version? my database still working in SQL Server 2K and the only thing I have to do is to re-install all my clients with the version 3.70??

    anybody can confirme this point?

    Thanks
    Nacho
Sign In or Register to comment.