Is there a problem with having gp10.0 and gp2013 on a client machine?
*This post is locked for comments
Is there a problem with having gp10.0 and gp2013 on a client machine?
*This post is locked for comments
I didn't have to do that because my gp10.0 is on a different server than my gp2013 server. I have two odbc connections one pointing to 10.0 and one pointing to 2013. It doesn't seem to be affecting each other.
No, I mean while installing Microsoft Dynamics GP, when you get to the "SQL Server window", you will have an option to enter a customer name for the Dynamics database. If you do so, it will create a new DYNAMICS company on the SQL server without affecting the GP 10 deployment. Check the image below;
You mean ODBC?
Okay, we are clear now.
When installing Dynamics GP 2013 on the client machine, change the name of the Dynamics DB in order to be able to have both 2013 and 10 at the same client. If you don't change the Dynamics DB name, it will upgrade the existing GP.
Just for the record, on my test machine, I have GP 10, 2010 and 2013.
I am not upgrading my gp10.0 client version. I have made a install package from gp2013 server and we are testing. So I don't want to upgrade the 10.0. So if we have them both available on the same client machine is that a problem?
In case we are talking about the upgrade, when installing a clean installation of GP 2013 on a client machine, you will run the 2013 utilities to upgrade the database. Keeping the GP 10 application on the same client will not cause any issues since it will not work anymore after the upgrade.
The best practice is to remove the GP 10 and keep the clean installation of 2013
Your feedback is highly appreciated,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,214 Most Valuable Professional
nmaenpaa 101,156