JL>there is not enough memory to run Word and shuts down Word. He has 8
JL>megs of RAM. I uninstalled Word and re-loaded it with the same
AH>I run into the same problem if I have just finished a large printing
AH>program in WinFax. If I print a large fax (8 pages or so), then go to
AH>Word I get the same message. I usually leave windows, then restart. I
AH>think it is a Windows problem, not Word.
Microsoft help desk (in Canada) told me it's a Word6.x problem. 
When I asked if upgrading to Word7 would solve it, they said 
"Well, it won't happen as often".
They claim that "out of memory" arises from two causes:
        1) Edit/Undo information stored in the last paragraph mark 
           of the document. Workaround: File save/Close/Open 
           periodically.   
        2) Word is not releasing system resources associated with 
           file handles. Workaround: File save/Close/Open 
           periodically.   
Neither of these solutions is acceptable to me, as I'm running 
unattended jobs to convert 100s of documents.
I have noticed that after a long job, the window title bar 
flashes at a rate of about two per second, suggesting some 
furious file-closing going on back-stage.
LAST WEEK'S BIG DISCOVERY: If I tile all windows during the 
========================== running of a macro, my W95/Word6.x 
                           system does not lock up anywhere as 
near as often. Whereas before I could limp through 3 documents 
before seizure, now the conversion runs ten time as fast AND 
carries on until it hits a rather large document. 
Since my driving macro uses a table of filenames:
>        Open filetable
>        while filetable not empty
>                get next name
>                delete first entry in table
>                save and close file table
>                open, process and close the current file
>                open file table
>        wend
.. A crashed system neans that the offending item has already 
left the table. I note the name, reload Word, and carry on.
It's a WORD problem, according to Microsoft, but it's not a bug, 
Honest!
I hope this helps.
From: christopher.greaves@pro-mail.com
      christopher.greaves@ablelink.org
 * 1st 2.00b #6263 *  People and Computers
--- PCBoard (R) v15.3 (OS/2) 5
---------------