Batch problem with .iqx

Back

Batch problem with .iqx

Author	Message
zajac	zajac posted 11 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 28, Visits: 98	Thought I'd revise this thread. The timing issue was indeed due to instruction pages which I'd assumed would not be counted in the timeout element. Anyway, all sorted so thank you. Rather than start a new thread, I thought I'd let you know that I am still having problems with CTRL+Q on some machines. Sometimes it will work and other times it wont (forcing the CTRL+ALT+DEL to kill the script). This is more an FYI rather than question. I do however, have two questions for you 1) When using an encrypted file format, is it possible to get a batch file to use a password parameter so that I don't have to join all the scripts into one? At present, I program all tasks individually. I know using DOS I can put a password parameter in but I would rather launch everything using Inquisit. Is this possible? With encrypted files they ask for a password every time it opens a new script. 2) I would like to lock programs to a set use period in our clinic. This is so that after a study has been conducted, the scripts will no longer run and cannot therefore simply be copied and used without permission. Can I call a date value somehow in expression, and then evaluate this against a date value that I specify in the script? Using a binary variable I should be able to get the script to terminate. Cheers Ian.
	Reply Like 29
Dave	Dave posted 11 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 108K	Re. #1: No, that's not possible, I'm afraid. Re. #2: Yes, that would be possible. You'll want to read the script.startdate property /onexptbegin, validate that against your set expiry date and /stop accordingly.
	Reply Like 33