First, a couple of questions.
- Are you running on a windows platform
- Are you building an EXE?
I am sorry I am late to respond, but I needed to test this before I recommended it. If the answer to 1 is yes, you can use the windows task scheduler to launch your app and make your acquistion. If the answer to 2 is NO, then your cmd line switches will need to be a -- instead of whatever you like. You can read a file, if need be, to determine the length of the acquistion. The biggest benefit to this approach, is that you can have the system run this task, even if you are not logged in! Usually IT hates it when you leave domain computers logged in! And best of all, NO system resources are spent, no background app is running, and consuming whatever resources are required. Granted, there are not much given the suggested approach, but yet another app (one with a front panel open somewhere) running. I do not know about you, but I try to minimize the number of processes running at any given time. I have tested this, and even brought my computer out of hybernation and sleep modes to run the app! That is fantastic. I hope this helps.
Paul