CG> One file will do it, when the conditions are right, for example,
 CG> dragging lots of table/column boundaries, according to
     No tables/columns here.
 CG> My workaround involves tiling all windows prior to executing a
 CG> vulnerable macro. I even have major macros open (for editing)
 CG> several important macros and tile *them* prior to execution.
 CG> This speeds up execution by a factor of ten *and* inhibits
 CG> crashing.
     There are no macros here. Not even more than one file open.
     Lately, I found out that this happens only when working on
     files created in Word 6.0. Files created in ver 7 don't
     exhibit this problem.
     Regards,
  |  |          |\ |
  |__|baidullah | \|ubar   internet: ubaidullah.nubar@saudi.org
___ Blue Wave/386 v2.30 [NR]
--- InterEcho 1.19
---------------