Il 15/08/2007 20:41, Vanguard ha scritto:
So explain how YOU would better provide a representation of data in a
database and its organization or keyword associations that wouldn't use
the hierarchical representation used now by Outlook? How would YOU show
the hierarchy without folders, subfolders, and items? How would YOU
show that the items are records in a database without confusing users
that haven't a clue of what is a database?
Are you raving?
I'm ok with the way Outlook represents data: it mimics the usual
file/folder hierarchical structure to which users are accustomed since
years.
The problem is with the import function, which has an unexpected side
effect I would almost call "bug". Even more, thinking that you can avoid
this side effect by first exporting messages from OE and then importing
them in Outlook (at least, that's what Brian wrote; I didn't try);
there's no real reason why this kind of import should behave differently
from the direct one.
You're focusing on the Received date. You've already been informed on
how to add a column to show the Modified date. Your choice to ignore it.
Guess what? I'm so lucky that I don't need to use Outlook or OE
.
I encountered the problem on a friend's PC. She switched from OE to
Outlook and then wanted to archive all mails received before Jan 2007,
but this is not possible anymore. They're not a lot of mails, luckily,
so I already decided that she will keep them there until archive time
will come or maybe move them by hand when she has time, not a big
problem. I could also recover OE's dbx files from a backup (I already
removed them), and then try the export+import solution, but she had a
number of folders in OE so I think it's not worth the hassle.
Showing the Modified date is not a solution, because she wanted to
archive mails *received* before a certain date, which is what most users
commonly need.