How QR works technically.

A QR file is a zlib compressed XML file containing three sections.
The first section is an information header, describing version, title and so on.
The second section contains all the Graphical User Interface (GUI).
The last section holds the reply from the user.

The Work flow

The flow diagram shows the three steps from publishing over submitting to processing.
It all starts with you designing a form and deploying it. Step two is at your users, where they fill out a form and submits it. The last step is collecting the results by downloading and processing

QR Designer schematic.

A QR Form starts its life in the designer as an XML template. In the distribution phase, it is just an ordinary file that can be copied, burned or mailed.

QR Form reader schematic.

When the user fills out a form, he or she can submit it back to you. The QR Form reader has build-in mechanisms to save it as a file, upload it to a FTP server or attach it to a mail using MAPI.

How you receive, the form depends on how you designed it. Again, the reader can save a file, upload to FTP or attach to a mail. The choice is yours.

You have two ways to process an incoming reply. The simplest way is to use mail and view the form by opening the attachment.

If you need automatic processing, you must save the incoming form-file in a folder where the processing application can read it.

QR Catch schematic.

The QR Catch application reads multiple QR forms and converts them into one CSV file. If you have forms with different purposes, QR Catch divides then into groups of CSV files.

QR Data schematic.

The QR Data ActiveX library imports QR Forms into any application with a programmable COM interface for instance Visual Basic in Microsoft Excel. This also gives you total control in terms of how and what to read.

More information.

See the help files for detailed information about each product.

QR Designer.

QR Catch.

QR Data.