 |
|
| Video and Audio], Broadcasting and podcasting Real Time Media On The Net | |
|
[description], Story, any other text you want to use. Microsoft Great Plains Upgrade – things to consider and FAQ by: Andrew Karasev If you have Microsoft Great Plains and support it for your company then you need to know some technical details about Great Plains version upgrade and what is going on behind the scenes, which options do you have in case of Dexterity, VBA, SQL customization, additional complexity comes with migration from ctree/Pervasive to MS SQL/MSDE. What is upgrade in the language of technology? Upgrade has server and client sides. Server side - upgrade converts tables from old format to the new one. In general words - Microsoft Business Solutions developers may change table structure, append additional fields to add new functionality, things like that. Upgrade copies the table with changes to temporary table, then drops original table, recreates it with new structure and copies all the data from temp table to the newly created one. Workstation side - workstation is written in Great Plains Dexterity and has Dynamics.exe - engine and DYNAMICS.DIC - dictionary. These two plus all the additional files will be replaced with the new ones. Other dictionaries, such us REPORTS.DIC and FORMS.DIC should be also upgraded and upgrade will try to deal with them automatically. In some cases modified reports (in REPORTS.DIC) could not be upgraded and need to be recreated in the new version. What is customization upgrade? You should consider different types of customizations: Dexterity, VBA/Modifier, SQL, ReportWriter, Crystal Reports Dexterity Customization - being very short - Dexterity may have so called Custom Forms - these do not need upgrade - they should work as is. Then Dexterity may alter existing Great Plains forms (so-called Alternate Great Plains forms) - in this case Dexterity customization should be redone for these forms/screens. Plus additional consideration should be given to Dexterity triggers, shadow tables, etc. VBA/Modifier customization - Modifier allows you to modify existing Great Plains windows - it creates so called modified Great Plains windows, stored in FORMS.DIC. Usually modification is placing new buttons or fields, which in turn will be given VBA scripts (stored in DYNAMICS.VBA). VBA scripts may call something nice, like Crystal Report, or have some data access logic. Usually the old version of DYNAMICS.VBA workds with the new version. You may need to rearrange buttons on the modified form. SQL - you may have some stored procs for data integration, EDI or the like - if the addressed tables will be changed in the new version then you need to analyze your SQL code. The good news is - Microsoft Business Solution doesn't make a lot of changes since version 7.0, because Microsoft is now trying to merge the products it owns: Great Plains, Solomon, Navision and Axapta - and so has different priorities ReportWriter - MBS doesn't change tables, but it keeps changing Dexterity formulas used in ReportWriter original reports - this is the problem in so-called Modified Reports upgrade - usually you have these reports modified: SOP Blank Invoice form, SOP Blank Picking ticket, etc. If report can not be upgraded - it should be redone in the new version with some exceptions. Crystal Reports - the nice thing about Crystal Report - id doesn't need to be upgraded (if the fields in the tables exist in the new version - which is usually true statement) What is upgrade for third-party modules? Your Great Plains may have so-called third party modules: Mekorma, Kampdata, Horyzon, Wennsoft, Avalara, Truepay, Trinity, Intellisol to name a few Third party modules may have their own utility for upgrade. You just need to know that your third-party is ready for the new Great Plains version - if not - you just wait and stay on the old version. What is migration from Ctree/Pervasive.SQL 2000 to MS SQL/MSDE? MBS has migration tool. You need first to install Great Plains on SQL Server with exactly the same account/segments structure and then install migration tool (it is Dexterity chunk) on your ctree/Pervasive workstation - then, when you integrate the chunk - you will map it to target SQL-based Great Plains Company, select all system and company tables, click the button and it will move all your tables one-by-one. In the case when your Great Plains ctree/Pervasive has third parties - you need to check if the vendor has migration tool - otherwise you have to do manual move, use SQL Linked server to your legacy data Do I need consultant? It is probably good idea to have consultant to do the upgrade. We strongly recommend you to use consultant in the following cases You have Dexterity customization You are doing migration from Pervasive/Ctree to Microsoft SQL Server/MSDE, especially when you have third-parties without migration tools You have a lot or ReportWriter Modified Great Plains Reports You have old version of Great Plains: Dynamics or eEnteroprise 6.0 or prior - in this case you can not appeal to Microsoft Technical Support - it is discontinued Your Great Plains has more than 20 users and you have to have upgrade done over the weekend - if it fails - you have business problems You don't have support - in this case you have to select your Microsoft Business Solutions Partner and pay for the annual support/enhancement plan - you will get new registration key and will be ready for the upgrade Good luck in upgrading and if you have issues or concerns – we are here to help! If you want us to do the job - give us a call 1-866-528-0577! help@albaspectrum.com
stream media
Until recently, people used a technique called symmetric key cryptography to secure information being transmitted across public networks in order to make stream media shopping more secure. This method involves encrypting and decrypting a stream media message using the same key, which must be known to both parties in order to keep it private. The key is passed from one party to the other in a separate transmission, making it vulnerable to being stolen as it is passed along. With public-key cryptography, separate keys are used to encrypt and decrypt a message, so that nothing but the encrypted message needs to be passed along. Each party in a stream media transaction has a *key pair* which consists of two keys with a particular relationship that allows one to encrypt a message that the other can decrypt. One of these keys is made publicly available and the other is a private key. A stream media order encrypted with a person's public key can't be decrypted with that same key, but can be decrypted with the private key that corresponds to it. If you sign a transaction with your bank using your private key, the bank can read it with your corresponding public key and know that only you could have sent it. This is the equivalent of a digital signature. While this takes the risk out of stream media transactions if can be quite fiddly. Our recommended provider listed below makes it all much simpler. Real Time Media On The Net Index
|
Main Menu News for 18-Apr-24 Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Source: BBC News - Home Links Links Links |
Copyright © 2005. Name of Site here. Last Updated: Thursday, 18-Apr-2024 00:03:13 MDT.