I don't know WHY that's happening, but have you tried other threading methods? Such as a BackgroundWorker component or ThreadPool.QueueUserWorkItem? Does the error still happen?
Chris Thompson
2009-05-27 06:33:29