You can develop your own visual components, or you can use existing popular component libraries to enrich the user interfaces.

For example; you need an editor to be able to enter IP address, and you want to use such an editor both in the Windows environment and in the web environment. In this regard, you can integrate an existing editor or code the editor yourself to use in your Project.

You can develop codes in any .NET application development environment (Visual Studio.NET, Borland Developer Studio, Sharp Develop, etc.) and debug your code in these environments. The Project Designer will work integrated to the application development tool in your system.

Also, you can subject the scripts you have developed in the Project Designer and report scripts to a debugging operation.

The application you have developed can also run in 64-bit.

The errors during Project design are checked by the system and tested against all errors. If any design errors are encountered, a warning is issued and a guide on how to correct it is shown. Therefore, any design errors are prevented. For example; when a link made to a table is not made of the unique fields, the system issues a warning and forces the user to make links with the correct fields. Thus, even errors from inexperienced users are prevented. There are hundreds of design error checks like this.

In areas where data entry is done, multiple data approval methods are used to reduce user errors to a minimum and are as follows;
• Alphanumeric Data Size (entry of data bigger than the field size is prevented on the editor and dataset level)
• Numeric Data Size (Data entry is ensured to be within the minimum and maximum numeric values that the data type allows)
• Numeric Data Limit (Data entry is ensured to be within the identified minimum and maximum numeric values)
• Conditional Numeric Data Limit (data limit is checked according to condition)
• Required (User is forced to enter data to required fields)
• Conditional Required (necessity of data entry is checked according to condition)
• Read-Only (data entry to read-only fields are prevented on the editor-level)
• Conditional Read-Only (read-only fields are defined according to the condition)
• Mask (the user is forced to enter data appropriate to the mask on the editor-level. (Number, date, phone, postal code, etc.))
• Character Set (ensures data entry is done with only defined characters. (Uppercase, lowercase, only letters, etc.))
• Regular Expression (ensures data entry appropriate to the defined regular expression . (E-mail, phone, etc.))

The user-friendly interface provided to develop applications offers a comfortable working environment that does not tire out the user. As all designed Windows were developed within the frame of a certain standard, a user who learns to use one window shall be able to get accustomed to the other Windows with ease.
In order to prevent errors during data entry by the user, required fields are shown and if data is not entered in these fields the user is issued a warning.
Data size is limited through the editor by taking into account the data limit of the field, and data entry that exceeds the limit is prevented.
Before the operations are conducted, the user is warned in regards to the nature of his/her work, and the operation of the user is not conducted before approval from the user. For example; before deleting a record, the system will ask “Are you sure you want to delete this record?”, and if the user approves, the record is deleted.

All parts of the application that are desired to be developed in the Project Designer are designed in the Project Designer.

Designed objects; Windows, reports, database objects (tables, fields, indexes, views, methods), security identifiers (users, user groups, permissions), access trees, editors, etc.

It is suitable for multiple users to simultaneously develop an application. For example; when a user is working on a window, the other user knows which user is currently using that window and can only open the window in read-only mode and view it. If the user that first opened the window closes it, the other user becomes able to make changes on the window. Thus, multiple-operation is ensured in a secure way.

The design of the application Windows is done with the Project Designer. A design tool specialized to enable easy and effective screen design is used. The controls placed on the window settle by interacting with each other and changes to the window size during run-time are also automatically reflected onto the controls on the window, meaning that the controls enlarge or shrink in the ratio of change.

• “Project Designer” contains multiple reporting tools for reporting of data.

Supported reporting tools (Grid, Xtra Reports, Dashboard, Snap, Speadsheet)

• While reporting, you can intervene with the structure of the report using multiple script
languages. Therefore, you can conduct much more flexible reporting.

Supported script languages (VisualBasic.NET, C#.NET, JavaScript.NET)

Generated reports run on both Windows and the Web.
You can prepare OLAP and Cross-Tab reports.
You can create 2D and 3D Charts.
You can change the resulting reports into PDF, Excel, Word, HTML, etc. formats.
You can subject the data to formulas to generate new data and use these new data inside the report.
You can write the texts in “Rich Text” format.
You can use sub-reports.
You can generate Multi Language reports.

In order to run the Project you have created through “Project Designer,” you can create a Project on “Visual Studio.” You can open the source codes for libraries developed in “Visual Studio” through “Project Designer.” You can debug the source codes you have developed in Visual Studio while the Project is running.

While the developed Project is running, all operations are automatically recorded due to the infrastructure of “Project Designer”. By means of this infrastructure, information such as accesses to the application uses of parts of the applications, examination of records, addition / modification / deletion of records, previous states of modified or deleted data, etc. by users is recorded. If necessary, it is possible to revert to a previous version of a modified or deleted the record. Thus any data loss is prevented.

All objects defined in the Project can be subjected to security due to the user, group, and role security infrastructure. For example, things such as which user has the authority to use a button in a window, which users have the right to access a certain area, which users can only open in read-only mode, which users can modify, etc. can be defined. This can also be utilized in the security of records. For example; viewing and modification by certain users for records that have been subjected to a filter can be prevented.

The management of licenses after the selling of developed applications can be conducted easily and effectively with the “License Management Kit.”

With the installation and update tool, the installation of Windows applications or the updating of the application with the implemented changes on the side of the end user can be implemented very easily even by users that are not knowledgeable in the use of computers.