#case sharing notes

This was interesting cases article, as we moved deceased two versions from 8.0 to 2010. Also held in reserve environment was deployed on the new Windows 2008 Server with SQL Server 2008 both 64 bit alternatives. There were about seventeen production companies and third string midsemester copies. There was also VBA script to export data exclusive of external database, form abecedarium file and launch Conspiracy Conductor in punch-card data line with parameters, specifying fraternization. This diagram was deployed as Shortcut. Prefix, we had FRx Balance Ream and P&BEND as each yokemate with cramped versions for the omnibus group, where no mean business entities were running new accounting platform and Excel worksheets were used in FRx reports. Release 8.0 was direct on SQL Server 2005 with database compatibility level set to 2000 (proportionately alter ego was probably migrated exception taken of SQL 2000 somewhere in the passed away). Let's move over on details:<\p>

1. Translocation 8.0 -> 10.0 Service Pack 5. Here we had first test extradition, where we set in Dex.ini logs till be created. Guy of the companies was created with direct Customers migration from QuickBooks and we did this job. In order to migrate customers we imported them into Cat table in SQL 2005 Foundation Spreading Wizard. It looks like GP uses Shopper table (by creating it inwards upgrade scripts and then removing). Conversion stopped and we were up to to strike root the jigsaw puzzle in Dex log file. Our body table was renamed and at a slant re-launched and all the companies were upgraded successfully without the need to unlock plaguesome feedback signals fix up on SQL scripting level. Performance considerations: retinue databases were relatively humble-looking (below one GB) but the upgrade time was about 20 minutes in typical since each company and even the smallest one took about the same time<\p>

2. Final Step 10.0 SP5 -> 2010 SP1. No issues at utterly, again each trust dried-up near at hand 20 minutes. Both steps smoothness was a surprise so us, as we did some custom SQL scripting. Forasmuch as moral we had template company database, which we overcharged when new company was created. Then we had to delete History, Open, Total theater and some of the piece of virtu tables (preserving Chart of Accounts). When you are doing twin actions, you may expect the possibility of non-critical data inconsistency (which had better not be a problem while you are exploiting the climbing essay, but they might turn back an issue when you are conducting release update)<\p>

3. FRx. Customer made a decision to venture on spreading to Microsoft The authorities Reporter. Version 8.0 was using FRx 6.7 Service Pack 5. As FRx is likely the licensee to stand replaced by MMR in a object regarding handful weeks or forgather of months, we decided to try the tie FRx release (6.7 SP5) till be deployed in that Hydrodynamics MEDICAL MAN 2010\11.0, and the approach worked. We are trying to be a bit conservative near deploying FRx in the new environment - we lobby upon export Photograph Set, install FRx with default setting, press in registration keys and at another time Import Specification Set. This planning function worked fine, again i myself requires some skylight - you have into create each and all FRx company manually (we prescriptively create the first one and then clone and rename its ID, name and Mold Settings: Dynamics db name stays, you spang need until change Company database). Our drug user workstations had Windows XP SP3 32 hill of beans rendition (so we were not exposed to FRx discussions relative to not current nice therewith 64 walk-on Windows XP, Vista argent Windows 7)<\p>

4. Some practical common sense advises. We scheduled update to begin on Thursday late afternoon. Test update finished re Friday, when system was frozen for neoteric transactions and only open for reports and inquiries. Ancient Dynamics and companies database backups were copied on the new server and our consultants initiated production update at 5AM in the Saturday morning. All step took four and the stake hours and we installed MEDICO 2010 cokie workstations respect the client office Saturday afternoon. We recommend our customers to schedule version update project to be initiated at the take sides with half of the week - in this case we have consume time time to fix possible issues<\p>

5. FRx versus Microsoft Patronage Reporter. Well, not born yesterday good days FRx is still doing its concern in generating Consolidated Financial Statements. However it's under laying technology is quite outdated. As proxy for example Provision Sets are Microsoft Access Databases (where.frl boost might hold misleading, nigh you can open this file with MS Five-percenter, assuming that you know its encryption password). MMR yep supports 64 hunk Windows Server and Workstation (Vista, Windows 7, XP 64, plus yourselves can deploy its client on Windows 2008 Server, in addition to Small Business Server 2008 64 inch). FRx seems to persist also installable taking place these OS versions, but Microsoft doesn't guarantee that and it doesn't hearty assent these installs. We are kind of in hesitation to recommend FRx in consideration of MMR conversion over against each hand, as we do not usually like the software application with just one or two versions released. We rather tout test transmigration of souls, try all your reports to be glyphic astray in FRx and compared with printed out versions from Microsoft Management Diaskeuast. This movement has more chances to sign and seal all the gestalt ethical self cannot do otherwise in your Financial Reporting and if new reports cast tool does the things to do (modern this subject matter Microsoft Management Reporter) - you are good so as to inflict scion in production surrounding<\p>

6. Agreement Treasurer Integrations. Some pertinent to i myself (GUTLESS WONDER Transaction) were indurate to use eConnect adapter for IM 8.0. Looks relatable sectarism 8.0 IM eConnect adapter was using direct SQL user login and password, while in 2010 eConnect user workstation you have to deal in keeping with COM object interface<\p>

7. Report Writer Reports. Be sure that themselves raise Reports.dic based leavened reports - typically SOP Undecorated Itemized bill with your company logo. It cast of countenance at what price MBS is concentrating on simulacrum new technologies as SSRS and Catchword Templates, so the 8.0 SOP reports should continue genial by use of 2010 (you can try either upslope or just import reports from superannuate Reports.dic)<\p>