Release Notes Dub QuestionMaker, version 6.1

Design Questionnaire screen of Dub QuestionMaker:
	Lay out issues are solved when using the pipe sign (|).
	When question text contains the tags <table>, <tr>, <td> or <div>, a <div class="QuestFont" width="100%">...</div> will no longer be placed around it.
	Layout problems of single response/multiple response questions with 'Other' and/or 'None of these' items put in multiple columns have been resolved.
	Changes in the Messages form will now also be saved when closing the window with the x.
	No Access Violation will occur when previewing a TREE question using F8.
	It is not necessary anymore to rebuild the dataset after expressions have been added for an already existing variable.
	The order-ID number of forms is automatically regenerated to improve numbering for groups.
	It is possible to update the default fields/variables name, phone or company using an expression after which the initial value will be automatically moved from name to name1/name2, from phone to phone1/phone2 etc.
	The 'Uncheck item' feature of the expression now works properly.
Other changes in Dub QuestionMaker:
	When creating a new project, it is possible to choose a template from a library. Also, it is now possible to hide the buttons 'Next' en 'Back' in the template, using JavaScript that reads the value of <input type= "hidden" name = "CanGoBack" Value = "0/1"> and <input type= "hidden" name = "CanGoForward" Value = "0/1">.
	In the template the non-existing folder name <#ImageFolder> in the path of images has been replaced by 'DubImages/', which will make editing in DreamWeaver (or other HTML-suites) more easy.
	The creation of the progress bar has been extended: a library and an auto calculation feature is added.
	It is now possible to change the default language with another language ('Switch default language'). Also, two combination languages are added: 'Dutch & French [Belgium]' and 'English & French [Canada]'.
	In Response Dataviewer it is now possible to filter on range of dates.
	In multilingual CATI projects the actual language of the respondent is stored in the dataset, not the selected language in which the messages are displayed.
	The feature 'Optimise' does not delete the conditions of list manipulations anymore.
	No error will occur when using the Translate feature for a project that does not have languages anymore.
	Removed the feature that prevented sample records with an invalid email to be sent out again.