I do this often to process large amouts of data. Shawn has confirmed the process and also uses the logic to run many concurrent threads. It has no bearing on the number of processors in a system.
On a P3-800 MHz system where I first tested this a few years ago, I ran 25-30 concurrent threads, processed about 400 jobs in 15 minutes at 100% CPU load. The newer systems don't even break a sweat.
Basically, what I do is:
- Create an array of tasks to run
- Run the first 25 in the list
- Monitor the task load, and when it drops below a threshold, I run a few more tasks. I'm rarely concerned about running at 100% CPU load for short durations.
So - basically, the answer is yes - you can run several tasks.
If this is a login process, you might want to give my login script a try. It does the drive & printer mapping first so those resources are available, then can display text message files for user notification, and then run any number of commands via Shell, Run, or Call. Using Call even allows you to utilize the variables and UDFs in the main script, or from script to script.
Glenn
_________________________
Actually I
am a Rocket Scientist!
