Edward, In VB DoEvents() is intended to surrender control from your (possibly ill-behaved) to the OS so that other things can happen. it sort of seems t owork, but never in the way you think it will. As far as VFP is concerned, here's a guess... Is the fax stuff 16 or 32 bit? I suspect the former. Try setting AutoYield to .t., just for the form you use to call the faxing code. After you call the faxing code issue a DOEVENTS. Immediately after the DOEVENTS, issue INKEY(30) which will put VFP into a wait state for 30 seconds. I would guess the loop you are using is firing so rapidly that the FAX code doesn't get a chance. Finally - turn on all your logs in NT and find out what processes are executing. I'd guess it works in Nt because the fax code gets its own thread, so there's lots of time for modems to initialize, dial, etc. All the above is based on the SWAG principle of programming. Good luck Miles Thompson > > I have a 3rd party class that I am using to fax documents out of > Visual > Foxpro 5.0. The controls in the class are writen for C++, Delphi and > Visual Basic. I can use the classes fine on my NT machine, but when I > run > it on my Win95 machine, I get a timeout error. The company who wrote > the > fax class states: "Timeout errors may indicate that your program is > not > allowing Fax Plus enough time to run, due to too much processing > without > using DoEvents on occasion." I have not used Foxpro's DoEvent > command, and > I'm not sure if it is the same as VB's DoEvents. So what I did was > place > "_VFP.AutoYield = .F." in my startup program. In a loop that forces > the > program to wait for the faxing to be completed, I placed "DOEVENT", as > the > product's VB sample shows. When I run the program it just freezes. > Is > there anyone out there who is familiar with VB who could tell how to > permit > the contrl enough time to run? > Thanks Ed