2) using OneNote 2007 for mission critical information (not a great
thing to do with Beta software).
That one. I converted fully from 2003 to 2007. I know that 2003 files are
opened read-only in 2007, but that's pretty useless.
I know that using beta versions for mission critical stuff isn't the
greatest thing in the world to do, but it's really the only way I would
actually test anything. Software that just sits on my computer and that I
open for testing purposes only, almost never gets opened, because I don't
find the time for it. So I rather run the risk and use beta software for
mission critial stuff. Have I been burned already by doing so? Yes, of
course (not with OneNote though). If you are in the beta (judging by your
post, you might be), I'll invite you to take a look at the private
newsgroups and some recent posts of mine there (I'll point you the posts if
you email me). Still, I am continuing to do it. The only time I actually
open any Office 2003 program is when I need to verify how something looks
there compared to 2007, or when I am stopped by a bug in 2007.
It's a calculated risk that is in my opinion worthwhile taking. A
precondition of course is that you know what you are doing and can deal with
the software being beta. I would NEVER recommend to a normal user to work
with beta software. Using beta software for real work is really only for
people who can deal with annoyances, bugs, crashes, reduced efficiency,
reduced productivity and occassional data loss without losing their mind.
Preferably, those people also should have some clue how to recover from a
data loss. Also, they should NEVER work without a backup.
Patrick