Options

Using Nav 2009 Client for Nav 4.0 database

mr_hinomr_hino Member Posts: 5
Hi
Our company have recently bought a few new computers that are running Windows7. We are using Nav 4.0 which is not compatible with Windows7, there for we have to downgrade our computers or use XP Mode.

Can we instead use Nav 2009 client on those machines? We propably need to upgrade the license, but its worth it if we can avoid downgrading the computers or using Xp Mode

Answers

  • Options
    ara3nara3n Member Posts: 9,256
    we have a couple of clients running on 2009 and 4.0 db. You will need to have everybody on same version of the executable so everybody has to install 2009. These clients mainly upgraded for web service features.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Options
    David_SingletonDavid_Singleton Member Posts: 5,479
    mr_hino wrote:
    Hi
    Our company have recently bought a few new computers that are running Windows7. We are using Nav 4.0 which is not compatible with Windows7, there for we have to downgrade our computers or use XP Mode.

    Can we instead use Nav 2009 client on those machines? We propably need to upgrade the license, but its worth it if we can avoid downgrading the computers or using Xp Mode

    4.0 will run on Win7 if you have the latest hot fixes. But that upgrade has the same risks as going to 2009R2 executables. Basically test it and make sure it works and most importantly that performance is ok. If you have a small database you are probably OK, but if it is large or you have a lot of users, then you would be advised to get help to make sure it is done properly.
    David Singleton
  • Options
    mr_hinomr_hino Member Posts: 5
    Okay thanks... So it should be straight forward do install the 2009 client and connect to 4.0 database? Nothing happens with the structure/tables/keys of the database?
  • Options
    ara3nara3n Member Posts: 9,256
    The process is to do a NAV backup and restore. Compile all the objects. Make sure all of them compile. There could be a couple of objects that don't compile due to external components. If you are not using them, ignore them.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Options
    David_SingletonDavid_Singleton Member Posts: 5,479
    Is this SQL or Native?
    David Singleton
  • Options
    mr_hinomr_hino Member Posts: 5
    Its Native database... the plan is to use 2009 client on win7 machines and continue with 4.0 client on the older machines.
  • Options
    David_SingletonDavid_Singleton Member Posts: 5,479
    mr_hino wrote:
    Its Native database... the plan is to use 2009 client on win7 machines and continue with 4.0 client on the older machines.

    Native you wont have any problems.
    David Singleton
  • Options
    mr_hinomr_hino Member Posts: 5
    Okay thanks.. I will try to install it next week :)
  • Options
    bbrownbbrown Member Posts: 3,268
    mr_hino wrote:
    Its Native database... the plan is to use 2009 client on win7 machines and continue with 4.0 client on the older machines.

    Note the posting from above:
    ara3n wrote:
    we have a couple of clients running on 2009 and 4.0 db. You will need to have everybody on same version of the executable so everybody has to install 2009. These clients mainly upgraded for web service features.

    You need to upgrade all the clients. And also the server since this is native. Also don't forget NAS if there are any.
    There are no bugs - only undocumented features.
  • Options
    ssinglassingla Member Posts: 2,973
    mr_hino wrote:
    Its Native database... the plan is to use 2009 client on win7 machines and continue with 4.0 client on the older machines.

    As bbrown said you cannot have 4.0 client and 2009 client running the same database. Once you do a backup & restore (upgrade directly) on 2009 client, 4.0 client will not be able to open the database.
    CA Sandeep Singla
    http://ssdynamics.co.in
Sign In or Register to comment.