Serjer: making MS Office crash is a trivial task- just open a corrupt word or exchel document- and I can suggest numerous other ways.
Making Openoffice
betas crash is really a very hard task (I can suggest inserting and initializing an older ispell dictionary which crashes the program with not much effort), but since this thing produces fine quality .pdf and .swf files at no cost at all and manages fine MS Office documents IN and OUT, and it also now uses advanced macros which are NOT (yet) vulnerable to known worms, while using 1/4 of the HD space and 1/3 of the MSOffice resources, the only reason to prefer MSOffice would be the price...
Unfortunately for Microsoft, OpenOffice is "slightly" cheaper!
It also works under Windows, Linux, FreeBSD, MACOS X...
IMHO it's only shortcoming is that (unlike DTP applications like Quark Xpress, InDesign and CorelVentura) it supports only unicode fonts- so your old, gorgeous collection of true type fonts is not usable with it- but then the same applies for MS Office, excluding Office 95.
PS: Just noticed the most important RC1 new feature: full support for the Python interpreter! that means OpenOffice now supports one of the best programming/scripting API's available, which is MULTIPLATFORM and at least as powerful as Visual Basic... in fact- much more easier to use, as Python has dummyproof FREEWARE windowed extensions like WxPython, while Visual Basic does NOT. In short, it is now very easy to build your own applications/scripts to work with OpenOffice, while MSOffice does not have this luxury yet- or at least, NOT for free.