Dub Interviewer Patch

Dub InterViewer 6.4.0.25
	DBLookup was saving fields with '_', for example entity_id. The '_' will not be saved anymore.
	Insert in MailLog sometimes has problem with an apostrophe ( ' ) in text, this has been solved with sqlString().
	Updating sample-property could not deal correctly with 'N' (broken numbers).
	E-mails that contained HTML, plain text and attachments were not formated correctly.
	E-mails that were not send due to 'time-out' were replaced in queue.
Dub InterViewer 6.4.0.34
	The possibility to change texts of TEXT-questions has been added.
	More extensive log in DoNumInclusion.
	DoNumExclusion: Log and exit when source is not found or empty to prevent Access Violation.
	Added lines in SetMemberQuestStatus to assign Questionnaire feature to other entity types.
	Online Report with variables and filters from different tables went wrong.
	Sometimes multiple definitions of the questionnaire was in memory. Changes have been made to prevent this.
	Sometimes Access Violation appeared when writing the Member Status to Dub Knowledge. This have been corrected to prevent this from happening.
	Recode: empty texts is not included anymore in the recode index (to prevent negative numbers).
	Recode: when the text is changed, the original text will get logged.
	Recode: after rebuilding dataset the rerun of recoding was causing an error.
	Manage Frames: in the screen 'Time group/zones' the time group will also be shown when 0 numbers are in the group.
	An error occurred when writing Text back when it contained quotation marks. This has been resolved.
	Sending Multi-part emails with attachment was not working correctly.
	DBLook up could not process fields with underscore '_'. This has been improved and DBLookup can now process fields like entity_id, they will be written as 'entityid' ('_' will be removed.)
	Failed messages due to timeout are re-queued.
	A double check was added to prevent a double instance of the questionnaire.
	'ReplaceVariable' raised exception when a field could not be found. This is no longer logged.
	Changed SMTP.ReadTimeOut and ConnectTimeOut to 60.000 (ms), because the 5.000 was much too low.
	Report with a counter on a variable together with a filter where these 2 variables came from different tables in the dataset, was going wrong.
	When unloading a questionnaire via background process the system now searches for all possible instances of the same questionnaire.
	Pressing option ‘Unload’ will first search for possible double instances and remove them, before actually unloading them.
	The system will catch a possible Access violation and still run the storage of Questionnaire Member Status.
Dub Tester 6.4.
	It is now possible to determine where the logs should be written/saved.
	No break of execution when the preferences can't be written (due to restrictions on PC)