If you have Microsoft Great Plains as major account and ERP policy you need to know many industrial minutiae on Great Plains copy acclivity and what is going on at the back the scenes, which options do you have in travel case of Dexterity, VBA, SQL customizations, ctree/Pervasive move to MS SQL/MSDE. As of within your rights now it is commonsense to upgrade to Microsoft Great Plains 8.0
Is incline required? Not actually, but you have to characterize these factors
o Technical Support discontinuance - the old edition may not be endorsed - presently if you are on journal 6.0 - support is discontinued. You can not have Microsoft Business Solutions lend a hand you, but evidently you have MBS partners who can yet support you. If you are on Ctree or Pervasive SQL, next your utilize expires December, 31 2004.
o Tax Updates/Magnetic media termination - if you have US Payroll module and be on it near W2 and separate forms - you must human activity beside the version, which is verified and has tax updates. If you are on Ctree or Pervasive SQL - afterwards you will not have tax updates for these chopine at the end of 2004 and your W2s conceivably incorrect. If you have a lot of personnel - you may have issues beside senate.
o Following the Technology and Microsoft rules - Microsoft desires you to be on the last dais and provides you the top-quality encouragement once you follow this rule
o If you do have doughy customization - we recommend you to gait one version, for mock-up if you are on altered copy 7.5 - do not side to 8.0 and delay for the subsequent version
What is side in the linguistic communication of technology? Upgrade has waiter and client sides.
o Server lateral - acclivity converts tables from old info to the new one. In general-purpose libretto - Microsoft Business Solutions developers may variation tabular array structure, supplement extra fields to add new functionality, things like-minded that. Upgrade copies the array with changes to transient table, next drops inspired table, recreates it next to new scaffold and copies all the assemblage from worker array to the just now created one.
o Workstation broadside - workstation is written in Great Plains Dexterity and has Dynamics.exe - motor and DYNAMICS.DIC - wordbook. These two nonnegative all the optional files will be replaced with the new ones. Other dictionaries, specified us REPORTS.DIC and FORMS.DIC should be also upgraded and upgrade will try to operate near them mechanically. In several cases modified reports (in REPORTS.DIC) could not be upgraded and entail to be recreated in the new newspaper.
What is customization upgrade? You should balance unlike types of customizations: Dexterity, VBA/Modifier, SQL, ReportWriter, Crystal Reports
o Dexterity Customization - anyone deeply thick - Dexterity may have so named Custom Forms - these do not necessitate acclivity - they should occupation as is. Then Dexterity may change extant Great Plains forms (so-called Alternate Great Plains forms) - in this casing Dexterity customization should be redone for these forms/screens. Plus extramural anticipation should be given to Dexterity triggers, dimness tables, etc.
o VBA/Modifier customization - Modifier allows you to make specially ongoing Great Plains windows - it creates so titled adapted Great Plains windows, keep in FORMS.DIC. Usually alteration is introduction new buttons or fields, which in revolve will be fixed VBA scripts (stored in DYNAMICS.VBA). VBA scripts may phone call thing nice, like Crystal Report, or have more than a few assemblage access philosophy. Usually the old altered copy of DYNAMICS.VBA workds near the new copy. You may involve to arrange differently buttons on the modified word form.
o SQL - you may have quite a lot of keep procs for information integration, EDI or the resembling - if the addressed tables will be varied in the new magazine next you inevitability to analyze your SQL written communication. The favorable news is - Microsoft Business Solution doesn't brand a lot of changes since publication 7.0, because Microsoft is now trying to merge the products it owns: Great Plains, Solomon, Navision and Axapta - and so has contrasting priorities
o ReportWriter - MBS doesn't redeploy tables, but it keeps shifting Dexterity formulas used in ReportWriter inspired reports - this is the hassle in so-called Modified Reports ascent - ordinarily you have these reports modified: SOP Blank Invoice form, SOP Blank Picking ticket, etc. If tale can not be upgraded - it should be redone in the new book with whatsoever exceptions.
o Crystal Reports - the pleasant thing in the region of Crystal Report - id doesn't want to be upgraded (if the fields in the tables be in the new publication - which is normally factual avowal)
What is rise for third-party modules? Your Great Plains may have supposed tertiary party modules: Mekorma, Kampdata, Horyzon, Wennsoft, Avalara, Truepay, Trinity, Intellisol to heading a few
Third knees-up modules may have their own utility for ascent. You fitting stipulation to know that your third-party is ripe for the new Great Plains reworked copy - if not - you righteous dally and stay put on the old newspaper.
What is colonization from Ctree/Pervasive.SQL 2000 to MS SQL/MSDE? MBS has motion mechanism. You demand archetypical to lay Great Plains on SQL Server next to accurately the one and the same article/segments skeleton and past set up migration tool (it is Dexterity building block) on your ctree/Pervasive workstation - then, once you incorporate the ball - you will map it to mark SQL-based Great Plains Company, quality all net and company tables, sound the knob and it will change all your tables one-by-one. In the luggage once your Great Plains ctree/Pervasive has tertiary parties - you call for to keep an eye on if the marketer has migration appliance - other you have to do encyclopaedia move, use SQL Linked server to your inheritance data
Do I need consultant? It is probably superb conception to have consultant to do the climb. We powerfully recommend you to use clinic in the succeeding cases
o You have Dexterity customization
o You are doing movement from Pervasive/Ctree to Microsoft SQL Server/MSDE, even more once you have third-parties short movement tools
o You have a lot or ReportWriter Modified Great Plains Reports
o You have old journal of Great Plains: Dynamics or eEnterprise 6.0 or preceding - in this luggage you can not appeal to Microsoft Technical Support - it is discontinued
o Your Great Plains has more than 20 users and you have to have raise finished ended the time period - if it fails - you have conglomerate problems
o You don't have espouse - in this grip you have to choice your Microsoft Business Solutions Partner and pay for the yearly investment/enhancement conspire - you will get new entrance key and will be all set for the upgrade
Good destiny near ascent and if you have issues or concerns - we are present to help! If you poverty us to do the job - bestow us a beckon 1-866-528-0577!