There are often questions about compatibility of 64 bit systems with Dynamics GP.

Below is a summary of the common questions for GP 2010 (Please refer to the System Requirements Page for the latest updates)

The following 64 bit Windows Clients are supported

• Microsoft…

This post was from Jivtesh regarding the compatibility of GP 10.0 & Tools with Windows 7.0.

I…

This post is long pending, since I had worked on the topic around 2 months back.

According to GP Installation Instruction, To set up an ODBC data source, enter the name you assigned to the SQL Server when you installed Microsoft SQL Server. A data source name called Dynamics GP also is created using SQL Native Client. If you don’t want to set up an ODBC data source, mark the Do not create a data source option.

It's very handy (and recommended too) to create the ODBC DSN thru' GP…

For those of you who follow me on Facebook and Twitter, you probably already got first hand updates as I was going through rebuilding my laptop with the new Windows 7 and getting all my core applications installed. Most of you are aware that I am more of a technical guy, so hardware and applications performance is very critical.

Let's start with my laptop... I currently own a Dell XPS M1710 running Intel Centrino Duo core and 2.5GB in RAM. I know, yes! I use a gaming notebook taking advantage of the processing capabilities and the massive 17" screen. A little outdated when compared to the new XPS, but it still gets the job done!

The goal was to install the following software:

• Windows 7 Enterprise
• Microsoft Office 2007 Enterprise, including Microsoft Project 2007 and Microsoft Visio 2007
• Microsoft SQL Server 2008 Standard with Service Pack 1
• Microsoft Visual Studio 2008 Standard with Service Pack 1
• Microsoft Dexterity 10 with Service Pack 4
• Microsoft Dynamics GP 10 with Service Pack 4
• Support Debugging Tool for Microsoft Dynamics GP 10
• Visual Studio Tools with Service Pack 4 for Microsoft Dynamics GP

In addition, I needed to install Microsoft Silverlight 3, Microsoft .NET RIA Services, Microsoft Virtual Earth Control CTP, and Microsoft Dynamics GP Integration Manager 10 with Service Pack 4.

After all, I am also gearing up for the Microsoft Dynamics GP Technical Conference, so I really needed to showcase all the latest technology -- well, I would have loved to have Visual Studio 2010, but Visual Studio Tools is not compatible yet -- to you the developers out there.

The prep work
I started out by backing up my all files onto my home NAS and progressed from there with a checklist of the most important programs I needed after the Windows 7 installation was complete. My goal was not to have a straight upgrade from Windows Vista Service Pack 2, but rather a fresh install as mostly recommended by Microsoft anyways.

Once backups were ready and the inventory of applications was completed came the actual installation of Windows 7.

Windows 7 installation.
I popped my copy of Windows 7 Enterprise into the DVD drive and rebooted my laptop. The first surprise was the now graphical installation interface, a long shot away from the old DOS interfaces that plagued previous Windows installations. The interface was pretty intuitive to navigate. I essentially started by reformatting my existing partion. This is where the second surprised come to play. In previous installations of Windows, formatting a partition could take long minutes. Windows 7 completed the reformatting of my 76GB partition in less than 10 seconds. From there on, copying the files and extracting them onto the hard drive was pretty simple. The footprint was minimal too, occupying less than 3GB.

As a laptop user, my major concern is always drivers. Windows 7 did an excellent job recognizing all my laptop components including the wireless... this was awefully cool because, the OS could immediately access other components available online and perform some basic updates at the same time the installation was happening. The only…

The good news: Microsoft Dynamics GP v10 is now compatible with Windows 7, the bad news: Microsoft Dynamics GP v9 is not! The Dynamics GP Product Management & Marketing team has announced it on their blog, however, the official stand on the System Requirements page on CustomerSource and PartnerSource won't…

aka "Why isn't my DSN showing up in GP? It's right there in the Data Sources window!"

This is one of those things that I am familiar with, but since I haven't run into it in a long time, I had to do some digging to find specifics of the solution. I'll post it here in case anyone else has the issue for the first time, and for myself when I forget again.

So far, I have used 32-bit Windows for my development virtual servers, but Windows 2008 R2 is only available in 64-bit, so I'll probably be using 64-bit Windows going forward for any new virtual servers.

As you know, Dynamics GP requires an ODBC Data Source Name (DSN) to be setup on the Windows machine where it is installed. It uses this to connect to SQL Server, and is usually very simple to setup.

But, if you install GP on a 64-bit version of Windows and manually setup a DSN, when you try and launch GP…

This one's quite baffling. The scenario is this:

1. I have my VBA Customizations on a 64 Bit Live Environment.
2. I wanted to setup a Dev Environment so that I can work on Enhancements and Additions. The Dev Environment is nothing but my laptop and it's quite obviously 32 Bit.
3. I had DBs restored from Live and GP installed with necessary addons on my laptop.
4. Imported Modifier/VBA Customizations from Live to my laptop. There we go with an error message, which I am yet to solve:

















And it took me to the VBA Editor. Since it said "VBA6.DLL is not found", I wanted to check whether all References are proper. And below is what I found:




















See the highlighted path and filename. It's completely different from what it has to be…

Hi folks, here is a situation we have come across with the Migration wizard for FRx Management reporter for Dynamics GP 2010.


Simply stated the issue is this:

The old FRx databases are Microsoft Office Access databases and so the migration wizard needs certain parts of office connectivity to be able to read and convert the old spec sets into the new FRx Management reporter for Dynamics GP 2010 formats (which are now stored in SQL tables).

FRx Management reporter for Dynamics GP 2010. will only install the…

Hi folks , this is a real quick handy hint. As you are probably no doubt aware Dynamics GP can not see 64 bit ODBC although it is compatable with  64 bit operating…

This post is a follow up to the previous post on the topic which discussed how you can use the registry editor to adjust the font files used for bitmap fonts to restore them to the default 100% DPI size.  If you have not read the previous post, please use the link below:

Windows 7, bitmap fonts and Microsoft Dynamics GP

As I hinted at in this previous post, any older applications that use bitmapped fonts such as MS Sans Serif, MS Serif and Courier are likely to have this same issue. 

I have already explained the logic behind the change in behaviour for Windows 7 which can automatically set the DPI to 125% during the install.  What has not been explained is why the bitmap fonts are not restored to 100% DPI when the DPI setting is changed back to 100% via…

Will DynamicsGP Version 10 run on Windows 7?
Why yes it will, thanks for asking.

Actually, all the pain we experienced with Vista has made this a non-event. There are even printer drivers that are labeled for use with Vista that work with Windows 7. Even the 64 bit version.

I’ve loaded GPV10 on 2 Windows 7 machines with success. The first install was on an old workhorse Dell Optiplx 760 with an Intel core duo and 1 GB RAM. This machine was loaded with Windows 7 Professional Edition. The machine was slow to launch GPV10, (as should be…