K
Ken
I've got a tmp file that bloats significantly (at least 15mb) every time I
run a procedure in a Word COM addin (written in VB6). The file (~WRS*.tmp -
actual name different of course every with every instance of Word) is created
when Word starts and deleted when Word closes. But if the procedure is run a
certain number of times in any Word session the tmp file grows so large that
it causes Word to crash with a not enough memory error.
I can't kill the file while Word is open because the file is in use.
I regularly flush the Word buffers throughout my code using UndoClear,
ScreenRefresh, DoEvents etc. In Word, it doesn't matter whether Fast save is
on or off, or whether background saves and auto recover are on or off.
This happens on Win2K/XP and with Word2K/2003.
I use several large arrays in the addin but erasing them at the end of the
procedure doesn't affect the size of the tmp file.
Any ideas on what's going on with Word and how I can either prevent that tmp
file bloat or reduce it after running the procedure?
Many thanks...
run a procedure in a Word COM addin (written in VB6). The file (~WRS*.tmp -
actual name different of course every with every instance of Word) is created
when Word starts and deleted when Word closes. But if the procedure is run a
certain number of times in any Word session the tmp file grows so large that
it causes Word to crash with a not enough memory error.
I can't kill the file while Word is open because the file is in use.
I regularly flush the Word buffers throughout my code using UndoClear,
ScreenRefresh, DoEvents etc. In Word, it doesn't matter whether Fast save is
on or off, or whether background saves and auto recover are on or off.
This happens on Win2K/XP and with Word2K/2003.
I use several large arrays in the addin but erasing them at the end of the
procedure doesn't affect the size of the tmp file.
Any ideas on what's going on with Word and how I can either prevent that tmp
file bloat or reduce it after running the procedure?
Many thanks...