Désolé, votre navigateur ne supporte pas le javascript. WINDEV AS/400 technical brochure
Cross-platform application development software suite Integrated software for developing cross-platform applications


WINDEV, WEBDEV and WINDEV Mobile are a complete Integrated Development Environment (IDE).

Application examples - above on Windows, below on a Web browser (left)
and on a Tablet (right).
ll with data from AS/400!

These Integrated Development Environments come with all the modules required for developing applications for individual users, network and Client/Server modes, for Internet or Intranet sites and for mobile devices.
rom the conceptual phase to the deployment of your applications, all the modules are included with the products.

"WINDEV AS/400" includes the full WINDEV version, plus the Native AS/400 Connector. This Native Connector lets you access AS/400 without using ODBC, OLEDB, or ActiveX, and allows you to benefit from all the features described in this document. "WEBDEV AS/400" is the version of WEBDEV that includes the Native AS/400 Connector. With WINDEV AS/400 you will be able to offer your users this type of applications, which will work with AS/400 data.

WINDEV and WEBDEV AS/400: AS/400 integration

WINDEV and WEBDEV allow for real-time, native access to AS/400 databases (without ODBC, OLEDB, or ActiveX), and give you access to AS/400 programs and commands.
t's revolutionary!
With WINDEV, you can exploit the AS/400 features and its UI in your development projects: the best of both worlds.
ou capitalize on your information system, while making the development process faster. Up to 10 times faster!
egardless of the client platform, Windows PC, Web browser, mobile device, etc., applications and pages are developed using the same 5th generation language.

Same well-known WINDEV programming. No AS/400 programming (RPG, Cobol, etc.) needed to use WINDEV AS/400. Program the applications built with WINDEV and WEBDEV automatically work with AS/400 data, if needed. Applications are portable straight away.

From the same application developed with WINDEV AS/400, you can access native AS/400 files, WINDEV databases (HFSQL), as well as other databases (Oracle, XML, etc.) and operating systems (Linux, etc.) with total transparency.
his allows you to keep your data where best suited and avoid duplication.
fter installing the Native AS/400 Connector, you won't have to perform any operation in AS/400.

All the AS/400 security features to access files and programs and to manage transactions are preserved.
our applications will be able to lock records and files opened in Read/Write mode, using the conflict management rules of AS/400, without interfering with other applications.

Applications developed with WINDEV or WEBDEV can send AS/400 commands, for example, to generate "OVRDBF" or "OPNQRYF" commands on data files before opening them with WINDEV commands, or to modify the work environment or allocate objects.

Native Connectors: security, speed and performance

Client computers running Windows benefit from the development power of WINDEV as well as the speed of native access to AS/400 data.
ith WINDEV AS/400 you can easily:
- Communicate with AS/400, without any specific development.
- Integrate the description of an AS/400 database to a WINDEV analysis.
- Read, update, insert, or delete records on AS/400 databases, in parallel with existing "5250" applications.
- Perform read or write operations in optimized mode (using buffers).
- Perform searches using simple or composite keys.
- Create transactional applications.
- Use Data Queues and Data Areas.
- Send CL commands using parameters.
- Call RPG, Cobol, and C programs and procedures using parameters.

Information System Architecture

It is very easy to configure the different workstations.
INDEV and WEBDEV communicate with AS/400 either through the APPC protocol of your router, or through TCP/IP.

Client computer: PC
. Windows 10, 8, 7, etc.
Any APPC router (Client access, NS Router, Netware for SAA, Microsoft SNA Server, PCS, etc.) or TCP /IP

Server: AS/400 or IBM i
. All OSs since version 4R3 included

The connection between the PC and AS/400 relies on the network architecture: Ethernet, Token Ring, SDLC, Twinax, etc.
f TCP/IP are used, a router is not required. If TCP/IP are not used, a router is required.


Let's illustrate the ease-of-use and the development power of WINDEV AS/400 using a concrete example: a sales management application.
EBDEV AS/400 and WINDEV Mobile rely on the same development method. In the deployment phase, only the runtime platform changes, while the UI remains the same: Browsers in WEBDEV, Windows in WINDEV and Pocket PCs, Smartphones or Tablets in WINDEV Mobile.

Note: to simplify the text in the rest of this document, we'll just use the term WINDEV. In this example, the application will run on a PC with data files on AS/400.

The development of this application can be broken down into 5 steps:

  1. Create the project and the "analysis" (DDS import)
  2. Use the RAD tool (optional step)
  3. Program the application
  4. Create the executable
  5. Deploy the application

These steps cover the usual development cycle. Each step can be completed with the standard modules included in WINDEV AS/400.


Let's create a new project in WINDEV (new application): a CRM project.

1st case: Import DDS (reverse engineering)

If there is existing data on your AS/400 database or your client's AS/400 database, simply import the DDS into WINDEV to use this data.

Then, specify the type of files that will be used in the application (you can modify this information later).
elect the option that corresponds to the desired type of files.

The data files can be of the following type:
- HFSQL (Client/Server database engine included with WINDEV and WEBDEV)
- xBase (*.dbf)
- Native AS/400
- External database (RDBMS such as: Oracle, Sybase, Ingres, Informix, Access, SQL Server, etc.)

The analysis tool requires an AS/400 connection.

WINDEV AS/400 knows how to access physical and logical files, the same way an application written in RPG (GAP) or COBOL would.
imply select the files needed for Client/Server development.
or our sales management application we will select the following data files:

WINDEV automatically retrieves the structure of the data files and creates a Metadata repository by reverse engineering.

Automatic data file structure retrieval by WINDEV
Automatic data file structure retrieval by WINDEV

WINDEV AS/400 converts AS/400 controls to Windows format. However, the data remains in AS/400 format.
ach of the logical files becomes a key for WINDEV (unique key in underlined bold, multiple key in bold only).
INDEV infers the relationship between the data files based on the definition of the keys. It then retrieves the integrity constraints defined for the AS/400 database.

The analysis diagram can be printed (along with the full documentation) using the documentation generation module provided with WINDEV.

2nd case: DDS export

If you want to create new files in the AS/400, simply define these files in the WINDEV analysis editor and export the DDS to the AS/400.

Then, select the file structures to export from the analysis.

For each of the selected files, the DDS are created and compiled on the AS/400, in the library of your choice (*LIBL).

WINDEV AS/400 converts PC controls to AS/400 format.

How does WINDEV determine if files exist on the AS/400?
After importing the files of the AS/400 into the analysis, you can define the different connection parameters. You can work with files from different AS/400.
o open a connection with a specific AS/400, simply use HOpenConnection.

Furthermore, for each file whose description has been imported from the AS/400 (DDS import), extended information is imported into the WINDEV analysis description.
he extended information about the file and the keys replaces the ".as" alias files used in previous versions.

How to switch from AS/400 to HFSQL and vice-versa?
You can change the connection with AS/400 files or HFSQL files at any time. HChangeConnection allows you to change the connection associated with a data file. This new connection will be used the next time the data file is opened.

Remember that, with WINDEV, programming is the same, regardless of the database (HFSQL or other): the source code is fully portable.

This technology allows for great freedom of development and deployment:

- You work for a consulting company that doesn't own an AS/400. Your client asks you to develop an application for AS/400, using existing data files.
n that case, you can import the DDS from your client's AS/400 and proceed with the development at your company,
on your computers, using local WINDEV data files (HFSQL).
hen, you can simply change the connection, and your application will work in Client/Server mode on the AS/400.

- You have developed an application with WINDEV AS/400. A client, who travels very often, wants to use this same application on their laptop. Simply transfer the application using the installer included with WINDEV, and dynamically change the connection (through a simple menu option, for example).
he application now works with the HFSQL data files located on the laptop (or on the mobile device for an application built with WINDEV Mobile).

- You have developed an application with WINDEV using HFSQL data files. Simply export the DSS to the AS/400 and define a new connection to work with data files located on the AS/400.

- You don't want to overload your AS/400 during the test phase. You can test your application locally by changing the connection.

- You want to make information available online on your Internet or Intranet site. If the data is located on the AS/400 and you don't want it to be accessible by Internet, simply convert this data to HFSQL format.


This method is optional.
AD means "Rapid Application Development". This technology allows you to create a fully functional application in a few minutes, using WINDEV.
n WINDEV, this technology generates all the processes required for managing data files in the analysis: create windows, pages, menus; modify, add or delete data; print reports, etc.

To generate the application or the site, simply answer a series of simple questions in the RAD tool.

WINDEV asks which type of code you want to generate: SQL, Object, Procedural, etc.
n our example we will choose "Procedural" because it is the type of programming generally used by AS/400 developers. Of course, you could also choose an object method (OOP), or several RAD patterns optimized for a given situation (remote access, etc.)

WINDEV generates the code to support concurrent access (lock records). These locks are recognized by programs written on the AS/400. AS/400 programs coexist with the programs written with WINDEV AS/400 and share the same data in real time.

You can define other parameters, such as the window size, menu background image, etc.
ou can also define your own generation patterns.

Then, you can select the data files from the analysis that will be included in the application.
eminder: in our example, the data files are located on the AS/400.

WINDEV creates all the windows and writes the associated code.

And that's it! The RAD tool has created the application!

To test it, simply connect to the AS/400 and run the application. <br /> ere's one of the screens automatically generated by WINDEV.

The application can be tested from the WINDEV environment or by creating an executable.

Example of a generated window: client form

All the read, search and link processes are generated automatically.

Imagine the time it would have taken without WINDEV!
Everything can be modified and customized: the style of the windows, controls, buttons, code, etc.

Program the application execution as seen from the AS/400

What happens on the AS/400 when a WINDEV program is running?
For each WINDEV application running, there is a physical connection to a job on the AS/400: here the EAC_CLIENT job.
his job also depends on the profile defined: here "WINDEV"

View of the EAC_CLIENT job linked to
the execution of our application developed with WINDEV.

The program running below uses the CLIENT data file and 1 key (either a physical (PHY) or a logical (LGL) key).
he "CL01CLUKEY" logical data file is the index for the "client numbers", the "CL02CLINAME" logical data file is the index for the "client names".

View of the I/O on the AS/400.
he I/O buffer can be set for each file. It will help you optimize performance according to your needs.

WINDEV's RAD (remember we use "WINDEV" indifferently for WINDEV, WEBDEV and WINDEV Mobile in this document) allows you to create an application, but you'll probably want to customize this application, add management rules, and more. You'll probably also want to develop some applications from the ground up.

verything generated by the RAD tool can be modified.

WINDEV comes with a query editor. It allows you to easily create queries using a wizard.

You can easily export a query result (to Text, Excel, World, XML, etc.) through a context menu automatically generated by WINDEV. It can also be used as a base for a printed form or a table.

WINDEV comes with a report generator.
t allows you to easily create reports from data files located on the AS/400 or the PC.
ar codes, images, labels and page backgrounds are supported automatically.

he result can be:
. a print preview,
. a printout,
. an HTML document,
. a PDF document.
he printer can be connected with the PC locally or through a network, but can also be defined as a "VIRTUAL PRINTER" of the AS/400.

Communication with the AS/400
WINDEV AS/400 lets you very easily use your AS/400 and iSeries legacy:
- batch or CL calls with parameters,
- support for Data Queues and Data Areas,
- execution of AS/400 commands (e.g. CHGPRF).

Various specific AS/400 commands are available in WINDEV AS/400:

ASCallRtv Runs an AS/400 command that returns variables (RTVJOBA type)
ASRtvResult Gets the result of the last ASCallRtv command
ASRunRPC Runs an AS/400 program that returns parameters
ASExec Calls all the AS/400 commands in the command line, in the context of the current session, with an AS/400 authenticated user profile
ASUser Changes the current AS/400 user profile to open a session with different privileges

After you've finished developing your application, you need to create the executable.
f needed, WINDEV will automatically manage a version number for your application.

WINDEV includes a version management module which allows you to restore a previous version of your application.

When creating the executable, WINDEV offers to create a native EXE file. The same program will work in Windows 10, 8, 7, etc. Thus, you don't have to worry about the target platform of your application when writing your code. The applications created with WINDEV will work on all Windows machines (on a browser, for applications developed with WEBDEV; and on a Pocket PC, Smartphone or Mobile device, for applications developed with WINDEV Mobile).
imilarly, with WINDEV you can easily create .NET assemblies, Web services and more: simply click the corresponding menu!


1. Installer WINDEV comes with a setup program generator. This module lets you create a custom procedure for installing your application. Everything can be customized. The features of this setup program are detailed in the documentation specific to each product.

Applications can be deployed via CD ROM, DVD, a network or the Internet.

2. Technical documentation
With WINDEV, you can print the full technical documentation of an application though reverse engineering at any time: analysis, screens, code, reports, etc.

You can define the level of details of the documentation.
his documentation can be generated in HTML, e.g. to share it on an Intranet, or as a PDF file to be included in an e-mail.
his will save you valuable time for future development projects.
his documentation is always up to date since it is based on the current state of your application.

WINDEV and WEBDEV are complete environments.


Please note that not all the modules included with WINDEV and WEBDEV have been described in this document, which focuses on AS/400. If you are not familiar with WINDEV or WEBDEV, our brochures are a good place to start.

If you want to develop "Client/Server" applications on AS/400, WINDEV and WEBDEV AS/400 are the best solution.
ower, ease of use, clear pricing, efficient technical support, high execution speed, compatibility with your existing elements, self-training within one week: all the assets for fast and powerful development are here.

See pricing WEBDEV AS/400

This page mainly focuses on WINDEV AS/400. However, WEBDEV, the development environment for creating dynamic Internet and Intranet sites, also supports this system.
t follows the same method and provides the same advantages.

Charts have the same aspect in WINDEV and WEBDEV AS/400.
ou can generate this type of chart automatically
for your end users via a popup menu.



I currently have WINDEV programs; can I transform them immediately into Client/Server programs for AS/400?

I have AS/400 data files, can I access them from the PC while other AS/400 applications are using these files?

If I write a Client/Server program for the AS/400 with WINDEV, would I be able to run it with files from the PC?

I don't know WINDEV, how long will it take to learn?
It generally takes an AS/400 developer one week. WINDEV comes with a tutorial.

I don't know AS/400, can I still develop applications?
Yes, you will just need to spend one hour reading the specific help section.

How come applications developed with WINDEV AS/400 are so fast?
Primarily because native access is very fast but also because the applications use the PC processor for data entry and display operations, thus freeing the AS/400.

I have an ERP system, can I develop add-on applications for it with WINDEV or WEBDEV?


1. How are the AS/400 locks managed and what is the difference with RPG programs?
With AS/400, an application can only set a lock per open file. When a lock is added, the previous lock for the same open file is canceled. WINDEV's "HRead*" functions manage these AS/400 functions directly.
ith RPG, you decide whether a file will be READ ONLY or READ/WRITE when opening it.
INDEV AS/400 uses the same principle. You specify a read option in your program (hLockWrite, hLockReadWrite). Additionally, WINDEV AS/400 has a new feature: implicit locks. Everything is managed automatically.

2. Can several AS/400 or IBM i be used?
Yes, the "Connections" option in the WINDEV analysis editor allows you to add several types of connections. Therefore, you can work with data files from different AS/400s.

3. Does WINDEV support version levels of AS/400 files?
Yes, LVLCHK (level Checking) should be added in the "advanced" information entered in the analysis. If this level checking exists, simply compare it to the real level and refuse the opening of previous levels.

4. Does WINDEV handle log files for AS/400?
Yes, log files are managed transparently by WINDEV log commands.

5. Does WINDEV handle files with members?
Yes, either through the WINDEV analysis editor or by executing a programming order (ASExec("ovrdbf(filename) on a file (libname/filename mbr(membername)).

6. How does WINDEV handle joint files?
In WINDEV, a joint file is considered as a regular read-only file with only one key. Simply import the DDS as for any logical file.

7. How do you call an AS/400 interactive program from WINDEV?
An AS/400 and a WINDEV program can communicate via a Data Queue.

8. How do you call a WINDEV program from an AS/400 menu?
You can create a WINDEV program that reads a Data Queue (fed by the AS/400 menu) whose task is to launch other programs.

9. Does WINDEV handle logical elements with omissions or conditions?
Yes. Logical elements with omissions or conditions are not considered as physical file indexes. Simply add these files manually as indexes in the analysis and in the "advanced information" entered in the analysis.
ou can also use them as master files with only one index. You will only need to import their DDS.

10. Can I manage DDM files from WINDEV?
Yes, WINDEV AS/400 handles DDM files transparently (files opened on one AS/400 that are physically on another AS/400).

11. Can several libraries be managed with WINDEV?
Yes. You can use files from different libraries, either through the LIBL file or by writing their name directly into the "advanced information". If a library name has not been specified, WINDEV AS/400 will search for the files in the LIBL libraries.

If you have additional questions, please contact us.


Here is a summary of the main features:
. Integrated Development Environment (IDE)
. Free Technical Support
. Free deployment
. Secure .EXE, J2EE Web Services, .NET and Linux applications
. Teamwork
. RAD: Complete application generator
. AAA (Automatic Application Architecture): create your own custom RAD for your teams
. Free option: Java RAD
. HFSQL, integrated Client/Server databases in Windows and Linux (free distribution)
. Third-party databases: Oracle, AS/400, SQL Server, DB2, MySQL, Access, xBase, and more.
Native XML
. Control Center for databases and deployed applications
. UML analysis center: code generated from the analysis, reverse engineering
. Creation of analysis and programming documentation through reverse engineering
. Business logic components
. Visual SQL generator
. Automatic UI creation with automatic style guide
. 5th generation language (5GL), write up to 90% less code
. Compatible with 4GL: C++, C#, Java, VB, Cobol, etc.
Import Access and Visual Basic applications
. Intelligent code editor with instant testing
. Refactoring
. Debugger
. Performance optimization center
. Up to 64 different languages per application
. Report generator (PDF, pre-printed form, bar codes, etc.)
. CHM help generator
. Integrated Internet access (page analysis...)
. UMC (User Macro Code): end users can add their macros to their applications
. AAF (Automatic Application Features): automatic export menu for end users. Export to Word, Excel, XML, PDF, 3D graphics, etc., automatic e-mail sending, creation of PDF files and more.
. RS 232 serial link, USB
. TAPI telephony
. Multimedia (image, sound, video)
. Version management
. Setup management center, automatic management of deployed applications
. Automatic test scenarios
. More than 100 detailed examples
. Self-training in 1 week (tutorial provided)