Originally Posted by
LaVolpe
Another option is to use a class structure for your server. Each class is a job, i.e., clsJobs, and has properties as needed (i.e., time started, completed, commands, description, which client sent it, etc).
The classes can be added to a VB collection. 1st job class in the collection, 1st started.
So when job #1 is complete (collection's .Item(1)), you can remove that item and the next job becomes #1, etc, etc, etc.
If you don't want to remove the job from the collection, don't. Just us another variable to indicate which index/job is current