Integrated software for developing cross-platform applications    Integrated software for developing cross-platform applications
WINDEV, WEBDEV and WINDEV Mobile
The WINDEV, WEBDEV and WINDEV Mobile environments are compatible and share project elements. It has never been easier to build multi-target applications.
Documentation overview
New Features
WINDEV
WEBDEV
WINDEV Mobile
Your applications are portable
If you’re in a hurry...
 
Diagram overview
Universal data access
Multi-platform development

Videos
Technical videos

They are using WINDEV
 
WINDEV AS/400 technical brochure

PRODUCT OVERVIEW

WINDEV, WEBDEV and WINDEV Mobile are complete and integrated CASE tool.


Application examples - above on Windows, below and to the left on a Web browser and to the right on a Tablet.
All of this with data from AS/400!

  

This means that they come with all the modules required for developing applications for single users, network and Client/Server modes, for Internet or Intranet sites and for mobile terminals.
From the conceptual phase to your applications deployment, all the
modules are included with the products.

"WINDEV AS/400" includes the full WINDEV product, plus AS/400 native access. The native access lets you access the AS/400 without using ODBC, OLE DB, 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 AS/400 native access. With WINDEV AS/400 you will be able to easily offer your users this type of screens, which will work with AS/400 data (read/write).


WINDEV and WEBDEV AS/400: integration with AS/400

WINDEV AS/400 and WEBDEV AS/400 allows for real-time native access (without ODBC, without OLE DB, without ActiveX) to AS/400 databases, and gives you access to the programs and commands of the AS/400.
It's not a mere retooling!
With WINDEV you can exploit the AS/400 features and its GUI in your developments: the best of both world.
You capitalize on your information system, while benefiting from reduced development times, up to 10 times faster.
Regardless of the client platform: PC running Windows, Web browser, radio terminal, the development is identical, using the same 5th generation language.

Programming is the same old WINDEV programming. No AS/400 programming (RPG, Cobol, and so on) is needed to use WINDEV AS/400. Programs built using WINDEV and WEBDEV automatically work with AS/400 data, if you need to. Application portability is immediate.

From the same application developed using WINDEV AS/400, you can access either the native AS/400 files, or databases in WINDEV format - HFSQL -, or both, as well as other database - Oracle, XML, and so on - or other OS - Linux, etc.- totally transparently.
This allows you to keep your data where best suited and avoid duplication.
After installing AS/400 native access, you won't have to perform any operation in AS/400.

All the security features of the AS/400 are preserved, for file and program accesses, as well as for managing transactions.
Your 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.

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


Native Connectors: security, speed and performance

Client stations running Windows with WINDEV benefit from the development power of WINDEV as well as the speed of native access to AS/400 data.
You can easily:
- Communicate with AS/400, without doing any specific development
- Get the description of a database (and its keys) located on AS/400 through reverse engineering (DDS import)
- Perform read, modify, add, or delete operations on the 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 DataQueues and Data Area
- Send CL commands using parameters
- Call RPG, Cobol, C programs using parameters


Information System Architecture

The machines configuration is very simple.
WINDEV and WEBDEV communicate with your AS/400 either through the APPC protocol of your router, or through the TCP/IP protocol.

The client station: PC
. Windows, 98, NT, 2000, XP, Vista, 7, ...
. Any APPC router (Client access, NS Router, Netware for SAA, Microsoft SNA Server, PCS, ...) or TCP /IP

The server: AS/400 or IBM i
. All the OS since version 4R3 included
. TCP/IP

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


THE DEVELOPMENT METHOD


Let's illustrate the ease-of-use and the development power of WINDEV AS/400 using a concrete example: a sales management application.
WEBDEV AS/400 and WINDEV mobile rely on the same development method. In the deployment phase, only the run-time platform changes, using the same UI: Windows with WINDEV, browser with WEBDEV, Pocket PC, Smartphone or Terminal with 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 the data files on the AS/400.

The development of this application can be broken down into 5 steps:
  1. Create project and "analysis" (DDS import)
  2. RAD (optional step)
  3. Program
  4. Create the executable
  5. Deploy the application

These steps cover the usual development cycle. Each one of them will involve the standard modules included in the WINDEV AS/400 product.


STEP 1: THE PROJECT AND THE ANALYSIS

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


    1st case: Import DDS (reverse engineering)

If you already have existing data on your AS/400 (database) or your client's AS/400, simply import the DDS defined on the AS/400 into WINDEV to use the data.

Then specify the type of files that will be used in the application (you can modify this information later).
Simply select the option corresponding to the type of files you want.

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


The analysis tool requires a connection with AS/400 then.

WINDEV AS/400 knows how to access physical files and logical files, the same way an application written in RPG (GAP) or in COBOL would do.
You only select the files needed for Client/Server development.
In our case, for sales management we select
"CLIENT", "ORDER", "ORDER LINE", "PRODUCT" and "SUPPLIER"

WINDEV automatically retrieves the file structure and creates a data referential for the reverse engineering development.

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

WINDEV AS/400 converts the AS/400 controls to Windows format. The data remains in AS/400 format, of course.
Each of the logical files becomes a key for WINDEV (unique key in underlined bold, multiple key in bold only).
WINDEV infers the relationship between the files based on the keys definition. The integrity constraints defined for the AS/400 are retrieved.

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



    2nd case: DDS export


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

Simply select the file structures to export from the analysis.

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

WINDEV AS/400 has converted the PC controls into 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 originating from different AS/400.
To explicitly open a connection with a specific AS/400, simply use the HOpenConnection function of W-Language.

Furthermore, for each file whose description has been imported from the AS/400 (DDS import), extended information is imported into the WINDEV analysis description tool.
The 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?
At any time you can decide to change the connection with AS/400 files or HFSQL files. The HChangeConnection function lets you change the connection associated with a file. This new connection will be used the next time the file is opened.

Remember that programming is the same with WINDEV, regardless of the fact that you are accessing HFSQL or third-party database files: the source code if 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 files.
You can import the DDS from your client's AS/400. You
proceed with the development at your company on their PCs, using local WINDEV files (HFSQL).
Then simply change the connection for your application to work in Client/Server mode on the AS/400.

- You've developed an application with WINDEV
   AS/400.

  Traveling sales people want to use this same application
locally on their laptops. Simply transfer the application
using the installer included with WINDEV, and dynamically change
the connection (through a simple menu option for example).
The application now works with the HFSQL files located on the
laptop (or located on the Pocket PC for an application built using
WINDEV Mobile).

- You've developed an application with WINDEV using
   HFSQL files.

  Simply export the DSS to the AS/400 and define a new connection
to work with 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 resides on the AS/400 and you don't want the
AS/400 to be accessible by Internet, simply converts this data into
HFSQL format.


STEP 2: RAD (OPTIONAL STEP)

This method is facultative.
RAD means "Rapid Application Development". This is a technology that allows you to create in a few minutes, using WINDEV, a fully usable application.
In WINDEV, this technology generates all the processes required for managing the analysis files: create windows, pages, menus, addition, modification and deletions processes, printed reports, and so on.

To generate the application or the site, simply answer the questions asked by the RAD tool (simple questions).

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

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

You can define other parameters, such as the window size, the menu background image, etc.
You can also defined your own generation models ("Patterns").

You then select the files (from the analysis) that will be part of the application.
Reminder: in our example, the data files are located on the AS/400.

WINDEV creates all the windows and writes the associated code.

The RAD tool is done creating the application!


To test the application, simply connect to the AS/400 and run the application.
Here's one of the screens automatically generated by WINDEV.

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

An example of a generated window: a client form

All the operations for reading, searching based on defined keys, linking the windows are automatically generated.

Imagine the time you would have needed without WINDEV!
Of course, you can modify and customize everything. the style of the windows, the controls, the buttons, the code, etc.


Program 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.
This job also depends on the profile defined: here "WINDEV"

In Client access, visualization of the EAC_CLIENT job link to the execution of our application developed with WINDEV.

The program running below uses the CLIENT file and 2 keys (or 1 "PHYSICAL" and 2 "LOGICAL").
The "CL01CLUKEY" logical file is the index for the "client numbers", the "CL02CLINAME" logical file is the index for the "client names".

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



STEP 3: PROGRAMMING

The WINDEV RAD (remember that we use the term "WINDEV" indifferently for WINDEV, WEBDEV and WINDEV Mobile in this document) lets you create an application, but you'll probably want to customize this application, add some management rules... You'll probably also want to develop some applications from the ground up.
Everything generated by the RAD tool can be modified.

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



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

Printing
WINDEV comes with a report generator.
It lets you easily create printouts from data files located on the AS/400 or the PC.
Bar codes as well as images are supported.
Background forms are also supported.
The result can be:
. a print preview
. a printout
. an HTML document
. a PDF document.
The 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.

Dialog with the AS/400

WINDEV AS/400 lets you very easily use your AS/400 and iSerie legacy:
- batch or CL calls with parameters
- support for DataQueues and DataAreas
- run AS/400 commands (CHGPRF for example),...

In WINDEV AS/400 some specific AS/400 commands are available:

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 with returned parameter values
ASExec the same without any parameters returned
ASUser Modifies the current rights (change user)



STEP 4: CREATE THE EXECUTABLE

After you've finalized your application, you need to create the executable.
WINDEV offers to automatically manage a version number for your application if you wish.

WINDEV includes a version management module which allows you to restore a previous version of your application: why not take advantage of this feature?

When creating the executable, WINDEV offers to create a native EXE. The same program will work in Windows 98, NT, 2000, 2003, XP, Vista, 7. Therefore you don't have to worry about your application's target when you write your code. The application created with WINDEV will work on all the Windows machine (and on a browser for an application built with WEBDEV, and on a Pocket PC, or a Smartphone or a Terminal for an application built with WINDEV Mobile).
Similarly, with WINDEV you can easily create .NET assemblies, Web services, trade components: simply click on the relevant menu!



STEP 5: DEPLOYMENT

1. The installer

WINDEV comes with a installation program generator. This module lets you create a custom procedure for installing your application.
Everything can be customized. This installer program's features are detailed in the documentation specific to each product.

The application can be deployed through, CD ROM, DVD, a network, or through the Internet.


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

The level of details of the documentation can be set.
This documentation can also be delivered in HTML, in order to be made
available on an Intranet for example, or can be delivered as a PDF to be included
in an e-mail.
You will again save precious time for your future developments.
This documentation is always up-to-date since it's based on the current state of your application.

WINDEV and WEBDEV are complete environments.




WINDEV AS/400:


Please note that all the modules provided as standard with WINDEV and WEBDEV have not been described in this document which is geared for AS/400. If you are not familiar with WINDEV or WEBDEV, we recommend that you discover them through our WINDEV and WEBDEV sales brochure.

If you want to develop "Client/Server" applications on AS/400,
WINDEV and WEBDEV AS/400 are the best solution.
Power, ease-of-use, simple price list, quality Technical Support, fast execution
speed, compatibility with your legacy, self-train within one week:
all the assets for fast and powerful development are here.

See price list


WEBDEV AS/400

This documentation presents WINDEV for the AS/400 environment.
WEBDEV, the tool for creating dynamic Internet and Intranet sites, works in a very similar fashion; it follows the same method and provides the same
benefits.


Imagine the look of your charts with WINDEV. Do you realize that this type of chart is automatic for your end user through the context sensitive popup menu

QUESTION/ANSWER

GENERAL QUESTION/ANSWER


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

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

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

I don't know WINDEV; how long will it take to learn?
It generally takes an AS/400 developer one week. A tutorial guide is included

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?
Yes



TECHNICAL QUESTION/ANSWER

1. How are the AS/400 locks managed?
What is the difference with RPG programs?

With AS/400 an application can only place one lock per open file. When adding a lock, the previous lock for the same open file is canceled WINDEV "HRead*" functions manage these AS/400 functions directly.
With RPG you decide whether a file will be READ ONLY or READ/WRITE when opening it.
The principle is the same with WINDEV AS/400, you specify a read option in your program (hLockWrite, hLockReadWrite). A new feature in WINDEV AS/400, implicit locks: everything is managed automatically

2. Can several AS/400 or IBM i be used?
Yes, the "Connections." option in the WINDEV analysis tool enables several types of connection to be added automatically. Therefore you can work with files originating from different AS/400s.

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

4. Does WINDEV handle file logs for AS/400 files?
Yes, keeping a log file is managed transparently by WINDEV log commands.

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

6. How does WINDEV handle joint files?
A joint file is considered a regular read-only file with only one key for WINDEV. 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 DataQueue

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

9. Does WINDEV handle logical with omissions or conditions?
Logical with omission or selections 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.
You may equally consider them as master files with only one index and it will suffice to import the 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.

WINDEV: EVERY THING IS INCLUDED
IN A TOTALLY INTEGRADED ENVIRONMENT


Here's a summary of the main features:
. Integrated environment (IDE)
. Free Technical Support
. Free deployment
. Create secure .EXE, J2EE Web Services, .NET and Linux applications
. Teamwork
. Real-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...
. Native XML
. Control center for databases and deployed applications
. UML analysis center, Merise; code generated from the analysis, reverse engineer legacy
. Analysis and programming documentation through reverse engineering
. Trade components
. Visual SQL generator
. Automatic UI creation, with automatic style guide
. 5th generation language (5GL), eliminate 90% of the code
. Open to 4GL: C++, C#, Java, VB, Cobol...
. Import Access and VB 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,...)
. CHM help generator
. Integrated Internet access (page analysis...)
. UMC (User Macro Code): the end users can add their macros to their applications
. AAF (Automatic Application Features): automatic export menu for the end user: export to Word, Excel, XML, PDF, 3D graphic... automatic e-mail sending, PDF creation
. RS 232 serial link, USB
. TAPI telephony
. Multimedia (image, sound, video)
. Version manager
. Installation management center, automatic management of deployed applications
. Automatic scenario test center
. More than 100 detailed examples
. Self train in 1 week (manual provided)