After further testing, this seems to be a thread locking problem within our program. Our program works - or not - depending on how busy the machine is. The only reason it turned up only during debugging was because the debugging of course required more cpu cycles. Sorry for the noise. -- Arvid Brodin Enea LCC