Microsoft Dexterity or former Great Plains   Dexterity was designed in earlier 1990th     with assumption that C programmi...
Dexterity architecture was transferred to MS Visual C++somewhere around 1999 with some additional bug fixing work,however ...
  Microsoft Dexterity, comparing to old Dexterity had toemphasize MS SQL Server stored procedures calls and scripts&n...
  Still good idea to keep dex screen developing, following byeConnect object oriented logic behind   As Microsof...
  This approach still requires some experience with Dexterityprogramming: DEX_ROW_ID, DYNAMICS DIC dex source codepro...
  Unicode – this is real problem   We often hearcustomer questions about dex supporting Unicode: Chinese,Japane...
  However some tools can help, Crystal reports for example –we have hybrid cloud to express pessimistic view here Ex...
hybrid cloud
Microsoft-Dexterity-Or-Former-Great-Plains-Dexteri1
Upcoming SlideShare
Loading in...5
×

Microsoft-Dexterity-Or-Former-Great-Plains-Dexteri1

226

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
226
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Microsoft-Dexterity-Or-Former-Great-Plains-Dexteri1

  1. 1. Microsoft Dexterity or former Great Plains Dexterity was designed in earlier 1990th with assumption that C programming language will provide computer platform independence: Microsoft Windows vs. Mac or Solaris/Unix, plus database independence or at least easy switch: Ctree, Pervasive SQL/Btrieve, MS SQL Server, Oracle, DBII, etchybrid cloud
  2. 2. Dexterity architecture was transferred to MS Visual C++somewhere around 1999 with some additional bug fixing work,however pretty flawless   When Microsoft purchased GreatPlains Software on the edge of XXI Century, the basis of Dexteritylost its actuality – in fact Microsoft Business Solutions activelymoved toward phasing out all the other platforms, but MS SQLServer by introducing MSDE platform – free version of SQL Server,without some tools, however   LetÂ’s look at MS Dexterity fromthis angle: Database Access
  3. 3.   Microsoft Dexterity, comparing to old Dexterity had toemphasize MS SQL Server stored procedures calls and scripts  This meant that former Dex cursors (as being db platformindependent) lost their actuality   Now it is probably goodprogramming tone to use SQL Stored Procedures to speed up dexscripting from the side of database manipulations Dex Screens
  4. 4.   Still good idea to keep dex screen developing, following byeConnect object oriented logic behind   As Microsoft isemphasizing MS Visual Studio Net development options, here wewould recommend Dex screens to be filled with eConnect logic viaDLLs where you call either eConnect DLL procedures or XML webservices eConnect interface SQL Stored Procedures
  5. 5.   This approach still requires some experience with Dexterityprogramming: DEX_ROW_ID, DYNAMICS DIC dex source codeprogramming, dexterity atomic SQL stored procedures – youshould be familiar with these legacy dexterity features DexterityInternational Aspect
  6. 6.   Unicode – this is real problem   We often hearcustomer questions about dex supporting Unicode: Chinese,Japanese, Korean characters
  7. 7.   However some tools can help, Crystal reports for example –we have hybrid cloud to express pessimistic view here Extenderoptimism   eOne Extender is very promising tools, if you areend customer – it allows you to forget about dex proprietaryfeatures and concentrate on GP prototyping: tables, forms, reports,plus even dex sanscript logic – if you have this under your beltArticle Tags:
  8. 8. hybrid cloud

×