In addition, learning to write Windows API code is like learning to write code in an entirely different language. It’s much faster using a Windows painting tool than writing Windows GUI API Code by hand. Increase Your Productivity with COBOL sp2 We can insulate you from those types of headaches by giving you a COBOL programming interface which will not force you to re-write code in the future.Ī Few Sample User Interface Screens Created Using COBOL sp2Ī Tabbed Scrolling Data Query/Executive Summary Screen Created Only with COBOL sp2 Perhaps the biggest reason to avoid using API code is the fact that Microsoft has even dropped certain API functions or dramatically changed the way a particular function works. Even learning the commonly used API CALL’s is a difficult task for any programming staff. Microsoft Windows provides over 700 API CALL’s. The COBOL sp2 copybook named SP2.CPY contains all of the supported sp2 functions. Trying to mix a process driven program with an event driven program is only going to result in program implementation delays and more headaches because of the increased complexity of the program. COBOL programmers are used to programming in a procedural fashion. Event driven programs allow any event to occur at anytime during the processing of your application. Using API code involves writing programs in an event driven fashion.
Likewise, COBOL sp2 programming is accomplished in a very comfortable and traditional procedural manner. API code is very cryptic which makes it difficult for large groups of programmers to maintain applications.
API code requires significant programming staff re-training. If you decide to change environments in the future, your staff must re-write the API code for the new environment.ĬOBOL sp2 uses familiar COBOL for the programming interface.
If you want to run the software in multiple environments, your programming staff must support multiple versions of your source program. Additionally, there is no API code for UNIX character-based environments. Windows API code is very different than API code for other environments.
In addition, your COBOL source debugger may not even work with embedded API code in your COBOL program.ĬOBOL sp2 is 100% portable across many environments, API code is not. Using API code, maintenance costs will accelerate in the future, because program modification and debugging become more complex. Using API code in a COBOL application is like writing a mixed language program. API code is more like C Language code than COBOL. Because COBOL sp2 allows developers to continue writing in ANSI Standard COBOL 85 CALL USING statements to control screen handling, all of your applications can be written using ANSI standard COBOL instead of in much more complex and cryptic event driven code or a new programming language.ĬOBOL sp2 is a Superior Alternative to API Code for GUI screens in a COBOL ApplicationĬOBOL sp2 is superior to API code for GUI implementation in a COBOL application because COBOL sp2 allows you to control screens with a 100% COBOL programming interface. No Need to Write Windows API Calls or a New Programming Language with COBOL sp2Īpplication Program Interface code, or API code, is an option for displaying GUI screens from a COBOL application. Here is a screen capture showing the COBOL sp2 Panel Editor:
COBOL sp2, The 100% COBOL Solution for Graphical User Interface DevelopmentĬOBOL sp2 is a Graphical User Interface (GUI) Development tool which was designed specifically for professional COBOL programmers.