Dynamics,Partner,Newsflash,sup computer Dynamics GP Partner Newsflash: supporting old Great Plains v
----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc
Great Plains Dynamics and eEnterprise 7.0 and 6.0, Dynamicsand Dynamics C/S+ of versions 5.5, 5.0, 4.0, Great Plains Dynamics on PervasiveSQL 2000 or Ctree, Great Plains Accounting for DOS and Windows 9.5, 9.2, 9.1and earlier obviously should be either supported by Great Plains VAR, orconsultant or self supported by your IT team. In this small publication we would like to review typical Dynamics GP orformer Great Plains legacy version support routines: 1. Going over 2 GB MSDE database limit. This problem is attributed to Dynamics GP 7.5and 8.0 on MSDE 2000 DB. The solution issimple you have to call your Dynamics GP Reseller and have them request new registrationkey from Microsoft Dynamics subdivision of Microsoft. Even if you are currently not enrolled inDynamics GP annual enhancement program (which might be likely the case,otherwise why would you stick to legacy historical version of Great PlainsDynamics?). In the case when you are notsure who is your Great Plains Partner, call Microsoft directly or our office,see the phone below. New reg key shouldallow you to move Dynamics GP to MS SQL Server 2000 Standard. If you need Database maintenance to send DBsize back below 2GB call us for help 2. Updating Payroll Tax. If you are on SQL Server platform, you canstill get tax table update. Thetechnology is simple we use current version of Dynamics GP 10.0 to update taxesin Dynamics database and then we copy UPR tax tables to your Dynamics database 3. Closing the year. Please, be sure you have made a backup ofyour Great Plains company DB, then in Routines financials, close the year. Closing the year moves open transactions inGeneral Ledger to historical tables, which is pretty large DB reshuffling,especially if you are on Pervasive SQL 2000/Btrieve or Ctree 4. Purging history in AP, AR, GL. In Accounts Payable module transactions, suchas Vendor invoice and your Payment go to history automatically when you applypayments and credit memos to invoices and debit memos. Then they are ready for history purge. In Accounts Receivables transactions stayin open tables, even upon applying Payments to Invoices. Transaction purge helps you to meet free harddisk space requirements for older Windows Servers. Purging history is available in Utilitiesmenu 5. Legacy Great Plains support nationwide. We specialize in such a service and we serveyou nationwide via web sessions, VPN and remote connections
Dynamics,Partner,Newsflash,sup