Hi all, I have some ABL procedures for the extraction of data from an OpenEdge database (generic code foreach through _file etc.). I need to be able to run the code against OpenEdge 10 and 11 databases.

I need to be able to run the code against db files on their own as well as databases that are 'live' and served. I need to be able to run against databases served on 32 bit and 64 bit OE db servers. Can someone please tell me what dev license I will need to purchase in order to meet these requirements? I've been asking questions elsewhere but am not getting straight answers - I think I'm being told I will need a OE 11 32 or 64 bit (doesn't matter) dev tools license. Can anyone help me out please?

The development license does not care whether the databse lives on a server or resides on the local machine and whether it is serverd by a 32 or 64Bit datbabase server product. Cctalk Serial Communication Protocol. What development licenes suits your needs is much more determined by the platfrom you plan to use it and yor needs regarding development.

Jul 27, 2015 Question What dev license will we need. ( the developer license is also a client in this. As far as I know the Progress Developer and OpenEdge. OpenEdge Advanced Business Language, or OpenEdge ABL for short, is a business application development language created and maintained by Progress Software Corporation.

Cameo Anthology Rapidshare here. Furthermore, only a OE11 client ( the developer license is also a client in this regard ) can connect to OE10 and OE11 databases - connecting an OE10 client to a OE11 database is not supported and from what I know will not work. Basically there are 3 development products: • 4GL development - although you can buy it for the Windows platform too, it does only make sense on a non-Windows platform and / or for CHUI development, available since forever. Sap Grc Rar Configuration Steps. • Progress Developer Studio - full blown GUI development based on Progress' Eclipse plug-in, available since OE11+. • OpenEdge Studio - full blown GUI development based on Progress' AppBuilder written in the ABL, available since V9+.

As far as I know the Progress Developer and OpenEdge Studio cost the same. Plus, I would not go for the OpenEdge Studio as the AppBuilder is a product of the '90s of the last century. Therefore, if you are on Windows and want save $$ at any cost - you might go for the 4GL development license, but, If I were you and considering that you need an OE11 product anyways, I would go for the Progress Developer Studio. You need to be aware that almost all you get with the 4GL developer studio is the procedure editor ( functionality-wise you might compare it with notepad courtesy of Windows ) and the ability to compile.

Heavy Regards, RealHeavyDude.

Emma,Thanks for your review of the non-production licensing of MSDN and VS. I have worked at companies that use this approach, so it was familiar to me.I have a similar but somewhat different situation under consideration. The site has a smaller number of developers, and uses traditional developer tool licenses such as Visual Studio 2005 / 2008 Professional Edition (instead of MSDN licenses). They have a number of SQL Server database environments (using a mix of Standard and Enterprise Edition; 2000 and 2005) that are licensed using traditional per server or per processor licenses – some production, some non-production (test, development, user acceptance test, demo, etc.). I have read up on SQL Server Developer Edition, which has all the capabilities of Enterprise Edition but is limited to non-production use (much like the server licenses in MSDN). The license model also sounds like an MSDN license – per developer with unlimited non-production use.The big difference that attracted me to possible use of SQL Server Developer Edition is the cost: $50 per license (one developer / user, unlimited non-production DB server instances).

In contrast, I believe that MSDN licenses are hundreds to thousands of dollars per developer per year (my recollection of MSDN costs may be dated and imprecise, but I recall the costs to be significant).Have you explored the licensing models and implications of SQL Server Developer Edition? Do I understand these licensing models correctly?Building on the production versus non-production use, many environments are clear in understanding which is which.

But what about something like a user acceptance test environment. Sme business unit users (not all) will access the system to confirm that specific functions are working as expected (hence the name for the environment), but it is not a true “production” environment in the sense of running the business from that environment. What is your take on fuzzy environments such as user acceptance testing regarding production or non-production use? Have you encountered similar examples elsewhere, and under what environment names? If user acceptance test is a non-production environment, would each business user “tester” also need a SQL Server Developer Edition licenses as developers would? Or is this considered differently and not require such additional licenses?I appreciate any feedback you can give on these related topics.Thanks,Scott R.