CCE nv

CCE Protools development environment
  • Increase font size
  • Default font size
  • Decrease font size

CCE Protools development environment


  1. Hybrid configuration
    A hybrid configuration means that some of the programmes run on the server so users work on the server instead of the client. Therefore, you use the speed of your server instead of your PC!

    In CCE Protools the calculation and print programmes run on the server, and the input and consultation screens run on the client/PC. The client is only responsible for requesting the screens while the ‘heavy’ tasks are performed on the server. This allows LISA to work much faster than other packages and the network is not loaded down unnecessarily. As a result, the user profits maximally from the server's speed. Because of this principle, the client is free immediately after requesting screens thereby ensuring optimal performance.

    Because LISA mostly works on the server, it is not necessary to purchase new PCs, which saves money. A last advantage of the hybrid configuration is that we automatically execute repetitive programmes at certain times via a batch scheduler.
  2. Uniformity due to templates
    To optimise the transparency of our development environment, CCE Protools only consists of 2 templates, namely the browser and the print screen.

    The “print screen” template is for printing or calculations that are done on the server. The uniformity makes it easy for developers to get started in our development environment as long as Progress 4GL version 9 holds no secrets for the developer. Due to our years of experience, we allege that a developer with the required Progress knowledge can develop in our environment after only 2 days of training!
  3. Multilingual online application
    CCE has its own online multilingual environment within CCE Protools. As a result, the application changes in accordance with the user's language and LISA does not have to be closed.
    We have provided toolbars, titles and files from the Progress database in our application for everything that is language dependent in the application, namely messages, menus, etc. These files come right out of the Progress database and do not have to be translated by the developer.
  4. Audit database
    We have developed an audit trail within our development environment that enables users to register record detail historically. The details are written in files and in the database. This makes it possible to know from a certain record who made changes to a certain file in the past and when.

    Of course this is only for business-critical files such as bank numbers, third-party management, discounts and promotions, etc. where changes have far-reaching consequences. The big advantage is that both developers and users can see how a certain item has evolved over time. This makes nasty occurrences like fraud impossible.

    The audit trial is a parameter that is determined during implementation and is a must for every company.
  5. Menus and toolbars / menu generator
    In our development environment the items menu and toolbar are separate files in the database. Every title or menu bar is called up by the browser's template so menus and submenus can be constructed. The label is input in four languages per command item. As a result, accelerator keys and icons in the ‘up, down and insensitive mode’ can be linked and the icon's location on the screen can be determined. The ‘command’ menu is a standard part of CCE Protools. Via the security developers determine which user or user group has access to this command.

    The CCE Protools development environment has ‘a menu generator’ so every menu line can be made in four languages. An important item in this menu generator is that one can link a host-based character program and a client/server GUI program to a certain menu line.

    When developing the menu generator, we thought of several practical things like the update of an existing application with possible specific menus for custom-made software. So it is possible to export certain menu lines and submenus then later re-import them.

    In addition to classical security, which consists of users and user groups, menus and submenus can also be linked to certain applications as long as the user has access to the applications.
  6. Printer management
    Within the CCE Protools development environment, printer management is a separate application in which different printers and spoolers are defined. A printer does not have to be a physical printer. It can also be a Windows program like Word, WordPad, Excel or Notepad. Physical printers are defined in printer groups that are linked to certain users or user groups. The user can only select printers that have been parameterised in advance. Last but not least, programs can be directly linked to a printer and repetitive print jobs are possible via ‘a print scheduler’. The print jobs are started automatically at the anticipated time.

    As described above, on hybrid configurations the print assignment is performed on the server, not on the client.
the optimum finance & ERP software
Integrated, completely modular, contemporary & user-friendly accounting package.