CompuServe Messages

Hi Nelson, I tried the code you sent. The For loop with the MsgBox statement in it caused a UAE rather than an illegal function call. Not that that's a big improvement.<g> However, adding an x% = DoEvents() after the Shell made the UAE go away. But your code did get me one step further in the search. Here are may latest and probably finally findings since I've gone as far as my knowledge can take me. Whether a UAE occurs depends on the location of the cursor from the time the Shell command begins until it has finished and the program has *completely* returned to VB. If the cursor is over a form, a picture box, a label, list box, directory box or a file box, NO UAE occurs. These controls don't even have to be on the same form! On the other hand, a UAE *will* occur if the mouse cursor is over a frame, text box, any kind of combo box, a drive box, scrollbars, an option button or check box. The only common feature I can find is this. With the SDK SPY program, when you are selecting a window to monitor, as you move from window to window, Spy shows you information about the window you are pointing at. The last line of this display shows the window's 'style bits'. For all controls that cause UAE's, the third from the left digit in the style bits is always ZERO. For the controls that don't cause UAE's, the third digit is never zero. Unfortunately, I don't know how to decode these style bits. Well that's it. I don't know what else to do to track this problem down. KeithF