Crypt Trials Technology » Customization

Microsoft Dynamics GP Customization Support and Recovery Service

admin — Tue, 06 Jul 2010 01:58:28 +0000

If you have current or old version of Great Plains Dexterity custom add-on module, or another modification type, such as Modifier with VBA scripts or eConnect application (including the case when it is Microsoft Visual Studio .Net C# or VB ecommerce integration project), GP Integration Manager advanced customization with VBA events handling scripts, simple or Advanced ODBC data sources, Great Plains Macros (including such cases, when you are moving ongoing transactions and master records into such modules as Fixed Assets), complex reporting (FRx, SSRS, Crystal Reports, Report Writer), this small publication should give you initial highlights on what to do next and how to get further help:

1. Dexterity customization recovery. Great Plains Dexterity custom programming was very popular in earlier 2000th and we see large number of Microsoft Dynamics GP customers with Dexterity custom add-ons. If this is your case, please review your Dynamics.set file to locate custom module there (usually it has you company name listed in the name of the module), then find your Dexterity customization source code somewhere on your file server (or request it from your initial Dexterity programmer) – usually Dynamics.dic or Extract.dic with Dexterity Sanscript codes not stripped out (when you integrate Dexterity chunk – source codes are automatically stripped out and there is no way to recover them). If you are not comfortable and need help in reviewing your Microsoft Dexterity customization, please feel free to call our office, see phone and email below

2. Modifier with VBA modification recovery. In order to analyze your GP system and find out if it has Modifier modifications, please review your Dynamics.set file and see if you have modified forms dictionary (Forms.dic for main product) and if you have files with VBA extension in GP directory (these files would contain VBA scripts). In our statistical observations, VBA and Modifier are less popular, comparing to Dexterity customizations, however Modifier customizations could be extremely complex, especially when your former VBA developers used elements of Continuum (including Dexterity Sanscript codes into VBA scripts and switching GP modules contexts, from Dynamics to Intellisol for example). if you got one of these complex Modifier scripting examples, we recommend you to re-haul your Great Plains user workstation to port custom logic to newer tools: eConnect, Dexterity, Extender

3. Integration Manager historical integration recovery and upgrade. IM for earlier versions of GP was based on Great Plains workstation as OLE Server (before introduction of eConnect). You may expect light or heavy VBA event handling scripts in Integration Manager integrations, which could be dependent on unique UNC Path parameters and hardcoded User ID and Password. If you have eConnect connector based integration, attempt to port it to new computer should be combined with eConnect installation on that new hardware (please read eConnect documentation, especially related to Control Panel Component Services). Integration Manager could be perfect tool for Quasi Real time ecommerce integration to Dynamics GP, where you base your Source on Advanced ODBC Query (SQL Server View, including heterogeneous, where data is pulled from MS SQL Server and Oracle)

4. Dynamics GP Reporting. For older versions of Great Plains Dynamics (8.0, 7.5, 7.0, 6.0, 5.5, 4.0, 3.2, including Great Plains on Pervasive SQL / Btrieve or Ctree/Faircom) reports were traditionally designed on Great Plains Report Writer (GP module programmed in Dexterity). Newer versions of Dynamics GP (9.0, 10.0 and 11.0 – expected release in May 2010) has more options for Microsoft SQL Server Reporting Services (SSRS) and more traditional reporting tools, such as Crystal Reports, Microsoft Access Reporting and MS Excel. All the versions of Great Plains and Microsoft Dynamics GP deploy FRx Financial Reporting for such reports as Balance Sheet, Profit and Loss , Statement of Cash Flow and plus consolidated versions of these reports. FRx also allows you to base report on so called Reporting Tree (consolidation by company or by account segment or account wild card or segment mask). If you have to consolidate foreign subsidiary, which is on different Corporate ERP platform, such as SAP Business One or 1S bukhgalteria, you can export foreign branch financial statements or GL trial balance to Excel and consolidate Excel worksheet with Headquarters P&L or BS in FRx

5. eConnect SDK for Microsoft Dynamics GP. Initially this tool was introduced for Great Plains eCommerce programmers to open up back office Dynamics GP accounting for ecommerce shopping cart integration. Since then (2003) eConnect went through the gradual evolution and in our opinion it came to its maturity in Dynamics GP version 9.0 (better to deploy eConnect for Microsoft Dynamics GP 10.0 as this is current version as we write these lines in December 2009, new version of GP 11.0 will or should be released in May 2010)

6. Great Plains Customizations in International Environment. Before being purchased by Microsoft, Great Plains Software made substantial efforts to expand in Europe: France, Germany, UK, Ireland, Spain, Poland, Austria, Russia. However, since the time when Microsoft Business Solutions acquired Great Plains Software and its satellites: Navision and Axapta, MBS strategy changed. And this change is not a surprise – Navision was one of the leaders in Europe in late 1990th and as you could guess there is no sense to compete with Navision on European ground. Axapta, being initially developed and introduced by Damgaard Software in Denmark (perfect cluster of Corporate ERP and accounting application firms: Navision, Mac Hansa, Maconomy, Axapta). Currently Axapta is sort of rising star for Microsoft Business Solutions Worldwide and Navision has good positions in Europe and Dynamics GP is trenched in USA, Canada and English speaking World

7. SAP Business One Rising Star. This small and mid size business Corporate ERP application with elements of CRM, Service Management, Manufacturing and Discrete Production, eCommerce. SB1 is localized and certified with Russian, Chinese, Japanese, Korean, Brazilian tax agencies, plus you can switch languages from English to Russian or Chinese or Brazilian Portuguese

Great Plains Customization Technologies: Highlights for Software Developer

admin — Sun, 04 Jul 2010 15:55:20 +0000

When Microsoft acquired Great Plains Software and then integrated Great Plains into so-called Microsoft Dynamics ERP products family as Dynamics GP, modification tools became more Microsoft and .Net oriented, as you could expect. However in the initial design in earlier 1990th Great Plains Dynamics was intended as multi platform product and its fundament was built on new technology named Great Plains Dexterity. Considering complicated origin of GP, let’s review development tools:

1.       Dexterity. Great Plains Dexterity, as we already mentioned is the heart of GP design, and it is in turn written as the shell in C programming language to secure certain flexibility, especially the option to switch from one operating system or computer platform to another. Being very powerful and flexible, Dex doesn’t facilitate so-called rapid development scenario as it is not object oriented and it requires you as programmer to have several years of extensive Dexterity programming prior to participation in Dexterity programming project. Dexterity has its own scripting language Sanscript. Latest versions of Dex support such cool Microsoft technologies as COM objects and Web Services, plus you can call SQL Stored procedures from Dex code. To get quick tour into Dexterity architecture, you may install it from GP CD #2 and open Dynamics.dic file – this dictionary has core GP logic and it is written in Dexterity

2.       VBA and Modifier. We were watching closely the competition between various GP customizing tools. And we still think that Modifier should be reviewed prior to eConnect. Modifier is in essence the module, written in Dexterity, which allows you to add buttons and fields to existing screens of GP as well as take them off. To animate new fields you use VBA scripting language, often you use ADO technology to access GP tables from modified forms

3.       eConnect. This SDK opens for you GP objects: master records (customer, vendor, GL Account, employee, prospect) and work transactions (SOP invoice, Purchase Order, Payroll Entry). eConnect is based on encrypted SQL stored procedures, plus it has several layers of technology wrappers – in fact it is friendly for Microsoft Visual Studio C# or VB developer. If you are integrating eCommerce website with your GP back office, we recommend you to consider eConnect as the main integration tool, also consider Autoposting Server to post batches of SOP invoices in GP

4.       SQL Stored Procedures Integrations. If you think eConnect is too heavy and complex and you are comfortable to do light SQL insert statement to populate GP tables, then SQL scripting is an option. However, we discourage newcomers from trying SQL insertion prior to researching other integration tools first

5.       GP Integration. Of course integration is not the same as customization, however we would like to orient you here as well. GP traditionally has Integration Management Module. With current version 10.0 IM has new connectors – from now on you can use eConnect connectors to do integrating

Sap Business One Consultant Atlanta, Chicago Newsflash: Customization

admin — Sat, 19 Jun 2010 15:38:27 +0000

Sap B1 ERP is on the rise in gaining its ERP and MRP for small and mid-size businesses market share. This publication should help you in your next accounting software selection, as well as in deciding on who will be your SB1 VAR or Reseller and Implementation Partner. When you are in software selection phase you should see SAP Business One presentation and in this demo you should identify which functionality fits your business processes and where you might need modifications. We will give you highlights on SAP B1 software development and programming, plus integrations

1.       First, if you are programmer, please know that in SB1 you can only do select statement, but you can not modify or insert data into SAP B1 tables directly, as you probably did with your legacy ERP application, such as Great Plains, for example. SAP Business One installation controls your direct database access in order to prevent possible data integrity problems

2.       SAP Business One SDK programming. Your SAP B1 customization partner should give you custom logic estimation. Modification should be programmed in SB1 Software Development Kit. SDK programming should be entrusted into certified SB1 SDK developer hands, and SDK is available for SAP Business One Certified VAR. Programming itself could be done either in VB or C# in Visual Studio .Net. If your SB1 implementation crosses US borders, then you should know that your custom module should be separately compiled for A and B versions (where version B is international). Plus you should be aware about future SAP Business One customization upgrade cost – as custom code will need to be verified and recompiled in the new version. Current SB1 version is 2007A and B. If you are upgrading from 2005, you will need to recompile it

3.       SB1 Workbench and Integration methods. If you got it working with Excel templates and this is OK for you, then the following paragraph should be skipped. However if you do not like Excel way, you should consider ODBC queries instead, where you can go and try advanced SQL scripting: select, union, group by, having clauses for example

Great Plains Customization Tools: Dexterity, Modifier, Econnect, Auto Posting Server

admin — Mon, 31 May 2010 09:50:27 +0000

Microsoft Dynamics GP, or former Great Plains Software eEnterprise, Dynamics has proprietary EDI: Microsoft Dexterity. This tools really requires skilled programmer to do the job, and we do not recommend you to do dex modification on your own or try to come through Great Plains Dexterity programming learning curve. Instead you should probe yourself as GP developer with eConnect – C#, VB and SQL skills are helpful here, or even in VBA – this programming technique comes together with GP Modifier module. Let’s review the tools:

1. eConnect. This is Software Development Kit with sample codes in VB and C#.Net. At the end of the chain eConnect calls encrypted SQL stored procedures, which you can not modify, and you shouldn’t as these procs replicate Dexterity business logic, where eConnect has some features of Object Oriented Programming. eConnect was initially dedicated to eCommerce Microsoft Visual Studio developer, who is given the objective to integrate e-commerce website with GP ERP at the back end. eConnect has some restrictions, one of them is lack of batch posting ability, so we recommend you Alba Spectrum Posting Server

2. Auto Posting Server. Again, GP is written in Microsoft Dexterity and it has its internal logic, which is available for Dexterity source code developer. Posting Server calls GP Dex batch posting native logic to post batches in the queue. You, as SQL programmer should place batches, created in eConnect or Integration Manager into this queue table. In our opinion, this product is more flexible and gives you more control, than Autopost, developed by Parity Software, GP VAR from South Africa

3. Modifier with VBA. If you have comfort level in VBA scripting and past experience programming and modifying MS Excel, Access, Word or other office applications with VBA, the research this option of GP customizing. Modifier allows you to place new fields to GP forms and screens and then you as programmer can associate VBA scripts with these new fields. If you plan to alter DB, by clicking or filling up new fields, please be sure that you are familiar with Microsoft ADO technology

Dynamics Gp Consultant: Customization Design, Support and Upgrade

admin — Fri, 02 Oct 2009 10:26:09 +0000

Great Plains ERP or new name Microsoft Dynamics GP has large client base in US, Canada, Mexico, Central and South America, Caribbean, Australia, New Zealand, Pacific, UK and South Africa. It has also good MRP applications market share in Asia, especially in the countries, where English language is in use in business. As you would always like to have multiple options open in installing, implementing, customizing and modifying your Great Plains version, in this small publication we would like to give you more ground in this topic

1.       Great Plains Software Licenses Purchase. There are three MBS centers: US, Ireland (Europe, Africa, Middle East), Singapore (Asia, Australia and Pacific). You should locate Microsoft Dynamics GP Great Plains Reseller/Implementation Partner in your region accordingly. Some companies, Alba Spectrum is an example are authorize in all centers and sell GP licenses Worldwide. You can only acquire Great Plains licenses through Microsoft Dynamics GP VAR channel, they are not available from Microsoft Business Solutions directly to ensure GP implementation to be performed by Microsoft GP Certified Partner

2.       Great Plains Customization. As typical mid-market ERP application Great Plains has good exposure to software programmers for custom development, integration and reports design. We recommend you to review whitepapers on GP eConnect, as this tool is very friendly to C# or VB.Net developers. If you are looking to make professional customization for your ERP, please check out with GP ISV partners, who provides Great Plains Dexterity programming services

3.       Great Plains Support. Modern technologies, such as Web Sessions, VPN, RDC allow you to get Great Plains technician help remotely and save on consultant travel. Remote support also theoretically could be done instantly on demand

4.       Great Plains Version Update. GP Upgrade should be trusted to professional GP consultant. To

give you just some Great Plains upgrade examples. Upgrading to version 10.0, which is in time current – it is service pack sensitive. For example, if you have GP CD 10.0, you can only upgrade with RTM version from GP 9.0 SP2, if you are taking upgrade path from 9.0 to 10.0

Dynamics Gp Reseller Newsflash: Gp Customization

admin — Fri, 04 Sep 2009 13:54:02 +0000

Dynamics GP ERP is very robust platform for implementing custom business processes as addition to existing ERP and MRP logic. As Great Plains Dynamics is targeting mid-size and even large companies, you should expect that modification flexibility comes with certain level of technology complexity, where you should not expect generic programmer to turn around in couple of days and begin to program such proprietary Great Plains tools, as Microsoft Dexterity. However it is probably fair to say, that Visual Studio C# or VB .Net programmer should be able to modify and design Great Plains integrations in new SDK – eConnect. In this small publication we would like to give you orientation session on Great Plains modification tools:

1.       eConnect. This tool is the one that you try, when you are doing integration of your external application to Great Plains Dynamics GP. Good example is e-commerce web site project with shopping cart, turning to Sales Order Processing order or Invoice. We recommend you eConnect, even if you think that simple ecommerce integration should be naturally done in MS SQL Server Stored procedures. eConnect if fact is written in stored procedures (however procedure code is encrypted and you can not use it as the reference) – so it leads you on the new level, where you manipulate Great Plains objects: Customer, Vendor, GL account, Inventory Item, Sales Order.

2.       Dynamics GP Dexterity. This tool is in essence GP application shell, and Great Plains is programmed in Dexterity on the core level: tables, forms, fields, triggers, etc. Dex, however is not as open to you as eConnect, and it is rather proprietary technology, plus if you are end customer and not a Dynamics GP VAR, you have to purchase Dexterity programming license from Microsoft in order to do in-house Dexterity development. So, assuming that you are contracting Dynamics GP technology partner with Dexterity Software Development factory, you should be ready to design large or small scale unique add-on for your organization

3.       VBA and Modifier. Here you add fields in Modifier and attach VBA scripts to them, if you need to work with data insert and extraction, please use ADO connection. VBA/Modifier requires customization site enabler license

4.       Extender. This toll is the module, created in Dexterity and it opens to end user and often to somebody who is very familiar with technology, but who is not a programmer, to extend or modify Great Plains screens, plus create new ones

5.       GP Integration Manager. Being excellent tool for integrating, it also has limited instruments, allowing you to alter integration logic through VBA scripts, translation tables, etc.

Great Plains Dexterity ? Microsoft Dynamics Gp Customization Technology

admin — Fri, 28 Aug 2009 11:04:21 +0000

If you remember ERP players in 1990th, you would probably remember the technology trends and stakes: nobody could really say which OS will win: MS Windows, MAC, SUN Solaris, UNIX; plus nobody could also predict which DB platform will stay: MS SQL Server, Sybase, IBM DB2, Oracle, or somebody else. This was the IT environment, when Dex was designed and introduced as Great Plains Software Dynamics development environment, programming language (Sanscript) and customization technology. Addressing computer industry challenges, it was built on the following principles: OS and DB platform independence and as the proposed subsequence – longevity. Microsoft Dexterity currently is the basis for Microsoft Dynamics GP 10.0, the latest version, it absorbed new technological features and trends: COM objects, ability to be integrated with Sharepoint, SQL Server Stored Procedures calls, and others

1. Programming in Dexterity. Dex is not technically Object Oriented language, so it is really hard to program Dex by example, as you would expect in the case of C# or VB.Net. Plus Dexterity is associated with Microsoft Great Plains architecture, this is why programming Dexterity requires several years of GP technical support experience, including GP data fixing with SQL scripts, data conversion, where you feed data from legacy MRP system to GP tables. You should also be familiar with major GP screens: SOP entry, GL transaction, POP Purchase Order, Inventory item maintenance.

2. DYNAMICS.DIC. This is Dexterity built dictionary, please be assured, that Dexterity source code is stripped out and as a programmer you will not find there procedures and functions scripts. In order to analyze Dex power and functionality, please review Dexterity manuals, available on Microsoft Dynamics GP 10.0 CDs

3. Custom and Alternate Dynamics forms. Dexterity architecture allows you to build new forms, as well as modify existing ones. Alternate forms are typically the issue in GP version upgrade, so we recommend you to avoid existing form modification option. Instead you should consider Dex triggers to work with existing forms and modify logic with the trigger

4. Extender. eOne version of extender allows you to deploy Dex power not being Dexterity developers, however you should expect limitations

Microsoft Dynamics Gp 10.0 Customization Scenarios

admin — Tue, 25 Aug 2009 22:46:02 +0000

Microsoft Great Plains version 10.0 has a lot of new features, including changes in architecture and especially user interface. These new features dictate change in GP 10.0 programming and custom development. If you are using Great Plains since earlier versions: 9.0, 8.0, 7.5, 7.0, 6.0, 5.5 or 5.0 and your company ERP deploys tailored Great Plains business logic, chances are high that customized logic was programmed in Great Plains Dexterity. Let’s begin with Dex modifications overview for GP version 10.0:

1. Microsoft Dexterity 10.0. Surprisingly enough, but Dex is still similar to its old versions, however if you are Dexterity programmer you have to adapt your Dex code to new interface features: icons, color schema, etc. Here we suggest, that at this time there is no need to imitate Microsoft Vista and Office interface compliance: drop down menus, navigation arrows. Historical excurse to Dexterity – this IDE is written in C programming language, theoretically allowing you to resolve Operating System and DB platform dependence; when Microsoft acquired Great Plains Software, non-Microsoft platforms, such as Pervasive SQL and Ctree were abandoned and Microsoft Business Solutions decided to concentrate on MS SQL Server platform only – for Dex Microsoft suggested advanced MS SQL Server Stored Procedures support – obviously DB platform independence paradigm is no longer feasible. Maybe this Dex excurse seems non relevant to you, however if you plan to customize GP for your organization, you have to know the architecture and Dexterity platform

2. eCommerce for Microsoft Dynamics GP. E-Commerce is becoming one of the most popular modification routines. Here Dex comes to the secondary plan and new integration tool Great Plains eConnect comes on the first scenes. eConnect replicates GP Dex logic in SQL Stored Procedures and by doing so it boosts integration performance, however eConnect still has to validate GP business logic and in most of the cases it uses SQL cursors to replicate Dex cursors. Cursors are obviously very powerful in manipulating GP objects, but they are not optimal in performance, especially if you compare cursors with aggregated SQL select and insert statements. Another eCommerce dilemma is GP batches automatic posting – eConnect, which is bound by Dex architecture restrictions doesn’t allow batch posting; in order to post GP batches from eCommerce application you will need to deploy Albaspectrum posting server

3. VBA/Modifier. GP Modifier is at this time legacy modification technology. Modifier allows you to place extra fields and buttons to GP screens and VBA fills them with the logic

4. GP programming for Microsoft Visual Studio developer. If you are C# or VB.Net programmer, you should invest your time in eConnect research; eConnect has multiple interfaces – all of them are coming back to call eConnect encrypted SQL stored procedures

Dynamics Gp Customization: Great Plains Software Development Overview for it

admin — Sat, 22 Aug 2009 21:22:33 +0000

If you are reading these lines, likely that you need to understand your options in Great Plains Dynamics GP ERP tailoring, modification, integration, reporting or other sort of software programming and business logic improvement. First recommendation to you is to look for existing Great Plains add-ons, available from Great Plains ISV partners and resellers. But, likely that you have this step already behind you and now you are thinking about undertaking your own GP add-ons developing. Let us give your GP customizing orientation session:

1.       Great Plains Dexterity. Most of the add-ons for GP (supported by GP ISV VARs) are programmed in Great Plains Dexterity or new name is Microsoft Dexterity. Dex allows you to intervene into Great Plains standard business logic, add additional screens, reports, tables, triggers, procedures and functions, as well as strings, fields, constants. There are no limits in Dexterity on what you can do in the sense of Dynamics GP modification, including new product creation. However Dexterity is not really simple and requires professional Dexterity programmers to do the coding. In Dexterity customization project, especially when you are altering GP logic substantially, please be ready to expect the budget, comparable to initial Great Plains software purchase

2.       eConnect. This Software Development Kit opens GP for integrations with your peripheral applications: ecommerce, legacy databases, EDI compliant systems. eConnect is definitely easier in comparison to Microsoft Dexterity to program – and being optimistic, you should expect regular C#, VB.Net Microsoft Visual Studio programmers with some excurse to SQL stored procedures and architecture to be able to begin eConnect programming turn around in a week or so

3.       SQL Stored Procedures as integration option. If you are on older version of Great Plains Dynamics: 8.0, 7.5, 7.0, 6.0, 5.5, or even earlier, or if your integration needs are very modest – you have SQL Stored procedures and scripting as integrating option. If you are on Great Plains Dynamics GP version 9.0 or 10.0, we would like you first to review eConnect – as likely it will do most of the integration job for you in its encrypted SQL stored procedures

4.       Integration Manager, VBA with Modifier. There are additional options, especially when you have VBA programmer in staff. In this case you can alter GP Integration Manager logic with VBA scripts. VBA and Modifier is build upon OLE Server technology and might be considered as a bit obsolete technology, but it still does the job

Great Plains Microsoft Dynamics GP Customization Tools

admin — Sun, 21 Jun 2009 20:49:55 +0000

Several years ago, when Microsoft Business Solutions announced so-called Project Green, where all four Corporate ERP platforms, owned by MBS were supposed to be reprogrammed in C# or another .Net compliant scripting language and be ready for being repackaged as sweets, compatible in each other to form final ERP and MRP assembly, we got some doubts about such customization tools as Great Plains Dexterity, Modifier with VBA, Integration Manager. However, those old days are now over and Dynamics GP changed several versions (from 7.5 to current version 2010) and even couple of years ago we heard semi-official opinions from MBS that everything will be rewritten in eConnect and such not .Net compliant technologies as VBA event driven scripting will be phased out – but current situation reaffirmed old status quo. We are just back from Convergence 2010 in Atlanta. Microsoft Dexterity is back according to David Musgrave, and VBA and Modifier are back according to the same person in Microsoft Business Solutions. Of course this is our unofficial opinion, based on the what we have heard on Convergence 2010:

1. Dynamics GP Visual Studio Development Library. Here you can do wonderful development, assuming that somebody from Great Plains Dexterity team will help you in creating Dexterity tables (automatically included into GP security realm). Technically this tool is similar in its capacity to VBA scripting to Modifier, however it might be more friendly to Microsoft Visual Studio Developer in C# or VB.Net. According to David Musgrave, Microsoft Dexterity guru, it is better to consider multiple tools in Dynamics GP Modification. If your programmers are comfortable with Dexterity -fine, however if you are Microsoft Visual Studio shop – review the VS customization options

2. Great Plains Dexterity. Here we have to reassure you as Great Plains programmer that Dex is there and it is the customization tool to stay and endure. Great Plains Dexterity Software Development factory is available through recognized Dynamics GP ISV Partners. From the technology perspective Dynamics GP Dexterity is programmed in proprietary scripting language Sanscript. Being insider to Dynamics GP customization – Dexterity ad-on is typically distributed via Dex chunk file, which is being copied into you Dynamics GP Programming folder will automatically integrate itself into Great Plains User Workstation

3. The level to being official or affiliated with Microsoft. Alba Spectrum is Microsoft Gold Certified Partner. We have or should be exposed to current or internal circle Dynamics GP proprietary white papers

4. I am Andrew Karasev, who is Microsoft Dynamics GP MVP (Most Valuable Professional from 2005 through 2010 as we are writing these lines in May of 2010), I personally got a feeling that we as Dynamics GP Programming experts have at least as much as ten year to stick to Great Plains Dexterity programming commitment. And I am supporting Great Plains Dynamics since 1994

5. How to get further help. Please call us 1-866-528-0577, help@albaspectrum.com In case if you are located internationally our consultants speak English, Spanish, Chinese, Portuguese, Russian, Filipino