Blaise 5.4 is coming

First version of Blaise 5 ACASI in the upcoming 5.3.0 release

Blaise 5.3.0 offers a first version of ACASI. This means that it is possible to play audio files in the data entry program(s).

The following functionality has been added to make this possible:

In the resource database editor, it is now possible to store media files outside of the resource database. To accomplish this, all media elements now have a Url property, which can be used instead of the FileName property. When a Url is specified, the media element is not stored in the resource database, but will be loaded at runtime from the specified Url. Specifying a Url will clear the FileName property and vice versa.

Continue Reading

Blaise 5 Layout Training at CBS - 27 till 30 November, 2017

At 27-30 November, Statistics Netherlands will organise a Blaise 5 Layout Training, which is a four-day course for Blaise developers. It will focus specifically on how to specify and apply layout using the new tools in Blaise 5. The course is especially useful for existing Blaise 4 programmers who want to know more about how to make the transition to Blaise 5, or who want to know more about the new capabilities of Blaise 5.

New for this course is that it is divided in 3 parts:

  • New in Blaise 5 (for Blaise 4 programmers)
  • Blaise 5 Layout Basic: Layout Designer
  • Blaise 5 Layout Advanced: Resource Editor

For more information, have a look at the menu Support | Training. To register for this course, you can contact This email address is being protected from spambots. You need JavaScript enabled to view it.

Blaise 5 training in Heerlen, Netherlands

June 12-14, 2017, we gave a Blaise 5 Layout training at Statistics Netherlands. About 18 participants spent three days learning about all the new possibilities in Blaise 5. The group of trainees was very international; from Iceland, Macedonia, Finland, Czech Republic, Denmark, Turkey, Italy and Bosnia-Herzogovina.

We renewed the course, by splitting up the Layout Designer part and the Resource Editor part. The idea behind this is that in the future trainees can determine whether both parts are interested for them, and have the ability to only follow one of these two parts.

We really enjoyed the audience and giving the course, and we also got valuable suggestions to make the course even better for the next time. If you want to know more about this course in particular or other future courses in general, please email This email address is being protected from spambots. You need JavaScript enabled to view it. to stay informed. If you are located in North/South America, please email This email address is being protected from spambots. You need JavaScript enabled to view it. instead.


Blaise 5.2.5 Performance and Load tests

To give an indication of the performance of Blaise 5.2.5, we try to measure how long a page turn takes.

A page turn consists of 4 parts:

  1. The user initiates an action, and as a result, a request is sent to the server
  2. The server processes the action
  3. The server sends a response to the client
  4. The client processes the response, and renders a page

Steps 1 and 3 are dependent on network performance (provider speed, Wi-Fi speed, firewalls, number of users that use the network, …). Because we cannot control these variables, these steps are not included in the results that we present here.

We have conducted two types of tests: a single user test, in which we measure steps 2 and 4, and a load test, in which we only measure step 2. The first test (single user performance) has been carried out on 11 configurations, with varying operating systems and browsers. To guarantee consistent results, all our tests have been carried out in an isolated environment, consisting of a server park with 4 servers.

The results are as follows:




Test Type

Step 2 – Server

Step 4 - Client


Step 2 - Server

Step 4 - Client


Single User

0.12 sec

0.31 sec

0.43 sec

0.07 sec

0.14 sec

0.21 sec

Load Test (100)

0.11 sec



0.08 sec



Load Test (200)

2.26 sec



0.24 sec



Load Test (300)

7.81 sec



1.69 sec



This table shows that the MVC/Angular web data entry client performs much better than the ASPX/WebForms web data entry client, both server-side (step 2) and client-side (step 4).

Gaining deeper understanding