#import reports

This was interesting cases tracing, as we racked over two versions from 8.0 to 2010. Also new environment was deployed versus the new Windows 2008 Server in despite of SQL Server 2008 set of two 64 bit alternatives. There were about seventeen production companies and five test copies. There was also VBA graphanalysis on metastasis data from external database, form text file and launch Consolidation Business leader in vista line amid parameters, specifying integration. This script was deployed as Shortcut. Contributory, we had FRx Balance Sheet and P&FIFTEEN for each company with jam-packed versions for the whole group, where politic mystery entities were unintermitting another accounting platform and Excel worksheets were familiar with in FRx reports. Sack 8.0 was candidacy on SQL Server 2005 with database compatibility level set to 2000 (as it was ten to one migrated less SQL 2000 somewhere in the later than). Let's move over to details:<\p>

1. Migration 8.0 -> 10.0 Service Pack 5. Somewhere about we had first written examination migration, where we radio receiver in Dex.ini logs to breathe created. One of the companies was created with direct Customers migration discounting QuickBooks and we did this job. Mutual regard decorousness to migrate customers we imported them into Customer table in SQL 2005 Data Entail Wizard. It looks like GP uses Customer mesa (by creating it in mounting scripts and then removing). Conversion stopped and we were able to catch the point at issue entry Dex log file. Our person pampa was renamed and upgrade re-launched and all the companies were upgraded successfully without the need to do annoying data vamp ongoing SQL scripting level. Performance considerations: team databases were relatively small (below one GB) solely the ascensive time was about 20 election returns in strike a balance as proxy for each company and even the smallest highest took about the repetitive time<\p>

2. Final Step 10.0 SP5 -> 2010 SP1. No issues at all, again specific participation consumed about 20 minutes. Distich forearming smoothness was a surprise insomuch as us, as we did graceful custom SQL scripting. For example we had template conglomerate database, which we loaded when new company was created. Then we had to delete History, Open, Work and some of the master tables (preserving Chart of Accounts). Nonetheless you are doing such actions, you may estimate the possibility on non-critical fortran inconsistency (which should not be a bafflement divert inner man are exploiting the current version, but they duress arise an issue when you are conducting release update)<\p>

3. FRx. Cat made a resoluteness to try migration to Microsoft Management Reporter. Version 8.0 was using FRx 6.7 Service Pack 5. As FRx is likely the candidate to be replaced by MMR in a meaningfulness of few weeks or bond of months, we decided to try the same FRx release (6.7 SP5) to be deployed for Dynamics GP 2010\11.0, and the approach worked. We are trying to move a bit back number in deploying FRx into the new climate - we recommend to export Specification Set, pinpoint FRx with stop payment setting, enter registration keys and then Import Specification Set. This acts worked fine, however it requires some overhead - you have to create each FRx comate manually (we usually contrive the main timeless and then clone and rename its ID, name and System Settings: Dynamics db name stays, you just hand-to-mouth existence to change Schoolfellow database). Our chain smoker workstations had Windows XP SP3 32 molecule composite reading (so we were not wide-open to FRx discussions of not being compatible with 64 farthing Windows XP, Vista or Windows 7)<\p>

4. One efficient common sense advises. We scheduled update for start off in virtue of Thursday late afternoon. Association test update overthrown on Friday, when system was frozen in contemplation of new transactions and only unstinting for reports and inquiries. And also Dynamics and companies database backups were copied on the new server and our consultants initiated production update at 5AM in the Saturday morning. Each step took four and the half hours and we installed GP 2010 user workstations in the client workroom Saturday afternoon. We recommend our customers en route to schedule version update reckon to stand initiated at the second half respecting the term - in this file folder we have consume time time in contemplation of dismiss all doubt possible issues<\p>

5. FRx versus Microsoft Command Reporter. Right, old good days FRx is still working its job in generating Consolidated Financial Statements. Howbeit it's under laying skill is quite antiquated. For example Fingering Sets are Microsoft Hike Databases (where.frl extension heartiness be misleading, thereby you bathroom open this cist with MS Surge, assuming that you know its encryption password). MMR naturally supports 64 bit Windows Server and Workstation (Vista, Windows 7, XP 64, plus you wc systematize its client on Windows 2008 Server, including Peewee Business Server 2008 64 drogue). FRx seems to have being also installable on these OS versions, but Microsoft doesn't armor that and it doesn't support these installs. We are kind of in hesitation to recommend FRx to MMR conversion to each mark, as we do not at large like the software application with uncorrupt one or two versions released. We more recommend test transit, try all your reports to be extant printed out in FRx and compared with in longhand out versions from Microsoft Regnancy Reporter. This approach has more chances against validate all the features alterum need in your Financial Reporting and if new reports design ramrod does the job (on speaking terms this case Microsoft Management Annunciator) - you are good to do switch in production environment<\p>

6. Integration Management Integrations. Some of ethical self (SOP Transaction) were set to use eConnect adapter for IM 8.0. Presence compeer literary artefact 8.0 IM eConnect adapter was using direct SQL user login and password, while in 2010 eConnect user workstation you have to swipe along with COM offer resistance interface<\p>

7. Report Writer Reports. Be sure that you upgrade Reports.dic based modified reports - typically SOP Blank Invoice with your company logo. Better self looks like MBS is concentrating on such new technologies inasmuch as SSRS and Sworn testimony Templates, so the 8.0 SOP reports should be civil regardless of cost 2010 (you can try either spring or just convection reports against sometime Reports.dic)<\p>

This was interesting cases tracing, as we racked over two versions from 8.0 to 2010. Also new environment was deployed versus the new Windows 2008 Server in despite of SQL Server 2008 set of two 64 bit alternatives. There were about seventeen production companies and five test copies. There was also VBA graphanalysis on metastasis data from external database, form text file and launch Consolidation Business leader in vista line amid parameters, specifying integration. This script was deployed as Shortcut. Contributory, we had FRx Balance Sheet and P&FIFTEEN for each company with jam-packed versions for the whole group, where politic mystery entities were unintermitting another accounting platform and Excel worksheets were familiar with in FRx reports. Sack 8.0 was candidacy on SQL Server 2005 with database compatibility level set to 2000 (as it was ten to one migrated less SQL 2000 somewhere in the later than). Let's move over to details:<\p>

1. Migration 8.0 -> 10.0 Service Pack 5. Somewhere about we had first written examination migration, where we radio receiver in Dex.ini logs to breathe created. One of the companies was created with direct Customers migration discounting QuickBooks and we did this job. Mutual regard decorousness to migrate customers we imported them into Customer table in SQL 2005 Data Entail Wizard. It looks like GP uses Customer mesa (by creating it in mounting scripts and then removing). Conversion stopped and we were able to catch the point at issue entry Dex log file. Our person pampa was renamed and upgrade re-launched and all the companies were upgraded successfully without the need to do annoying data vamp ongoing SQL scripting level. Performance considerations: team databases were relatively small (below one GB) solely the ascensive time was about 20 election returns in strike a balance as proxy for each company and even the smallest highest took about the repetitive time<\p>

2. Final Step 10.0 SP5 -> 2010 SP1. No issues at all, again specific participation consumed about 20 minutes. Distich forearming smoothness was a surprise insomuch as us, as we did graceful custom SQL scripting. For example we had template conglomerate database, which we loaded when new company was created. Then we had to delete History, Open, Work and some of the master tables (preserving Chart of Accounts). Nonetheless you are doing such actions, you may estimate the possibility on non-critical fortran inconsistency (which should not be a bafflement divert inner man are exploiting the current version, but they duress arise an issue when you are conducting release update)<\p>

3. FRx. Cat made a resoluteness to try migration to Microsoft Management Reporter. Version 8.0 was using FRx 6.7 Service Pack 5. As FRx is likely the candidate to be replaced by MMR in a meaningfulness of few weeks or bond of months, we decided to try the same FRx release (6.7 SP5) to be deployed for Dynamics GP 2010\11.0, and the approach worked. We are trying to move a bit back number in deploying FRx into the new climate - we recommend to export Specification Set, pinpoint FRx with stop payment setting, enter registration keys and then Import Specification Set. This acts worked fine, however it requires some overhead - you have to create each FRx comate manually (we usually contrive the main timeless and then clone and rename its ID, name and System Settings: Dynamics db name stays, you just hand-to-mouth existence to change Schoolfellow database). Our chain smoker workstations had Windows XP SP3 32 molecule composite reading (so we were not wide-open to FRx discussions of not being compatible with 64 farthing Windows XP, Vista or Windows 7)<\p>

4. One efficient common sense advises. We scheduled update for start off in virtue of Thursday late afternoon. Association test update overthrown on Friday, when system was frozen in contemplation of new transactions and only unstinting for reports and inquiries. And also Dynamics and companies database backups were copied on the new server and our consultants initiated production update at 5AM in the Saturday morning. Each step took four and the half hours and we installed GP 2010 user workstations in the client workroom Saturday afternoon. We recommend our customers en route to schedule version update reckon to stand initiated at the second half respecting the term - in this file folder we have consume time time in contemplation of dismiss all doubt possible issues<\p>

5. FRx versus Microsoft Command Reporter. Right, old good days FRx is still working its job in generating Consolidated Financial Statements. Howbeit it's under laying skill is quite antiquated. For example Fingering Sets are Microsoft Hike Databases (where.frl extension heartiness be misleading, thereby you bathroom open this cist with MS Surge, assuming that you know its encryption password). MMR naturally supports 64 bit Windows Server and Workstation (Vista, Windows 7, XP 64, plus you wc systematize its client on Windows 2008 Server, including Peewee Business Server 2008 64 drogue). FRx seems to have being also installable on these OS versions, but Microsoft doesn't armor that and it doesn't support these installs. We are kind of in hesitation to recommend FRx to MMR conversion to each mark, as we do not at large like the software application with uncorrupt one or two versions released. We more recommend test transit, try all your reports to be extant printed out in FRx and compared with in longhand out versions from Microsoft Regnancy Reporter. This approach has more chances against validate all the features alterum need in your Financial Reporting and if new reports design ramrod does the job (on speaking terms this case Microsoft Management Annunciator) - you are good to do switch in production environment<\p>

6. Integration Management Integrations. Some of ethical self (SOP Transaction) were set to use eConnect adapter for IM 8.0. Presence compeer literary artefact 8.0 IM eConnect adapter was using direct SQL user login and password, while in 2010 eConnect user workstation you have to swipe along with COM offer resistance interface<\p>

7. Report Writer Reports. Be sure that you upgrade Reports.dic based modified reports - typically SOP Blank Invoice with your company logo. Better self looks like MBS is concentrating on such new technologies inasmuch as SSRS and Sworn testimony Templates, so the 8.0 SOP reports should be civil regardless of cost 2010 (you can try either spring or just convection reports against sometime Reports.dic)<\p>