If you want to send me--off list--your correspondence to and from Eric Fookes, I'd be interested in reading it. I have encountered none of those problems, and I'm not even sure how they could develop.
MBA imports whatever .TBB files you want, separated or merged however *you* tell it to do it, and then keeps it nameless, in memory, until/unless you save it as an archive. At that point, you can name it whatever you want. I have not had any of the naming problems you described, in importing or exporting, single mailboxes or multiple. (And all of this is just using the primary grid; it's all even more adaptable using the subset grid.) Generally speaking, I think exporting to .MSG messages is advisable only if you want to forward messages on to someone else; it's an Internet standard format. JN Geoff Lane wrote on Sunday, January 27, 2002: > MBA can't read Unix mailboxes and it derives its internal mailbox name > from the name of the file that contains the message text. All TB > message bases have the name "messages.tbb", so MBA dumps all those > messages into an internal folder with the name "Messages" -- so it > doesn't matter how many folders you have because MBA effectively > merges them. > I also tried exporting from TB to individual .msg files. Then, > creating mailboxes from filenames, MBA created lots of mailboxes > called "00000001", "00000002", ... Each folder contained files with > the same name but from different directories. So, it placed > ".\base1\00000001.msg" in the same mailbox as ".\base2\00000001.msg", > which ensures that no two messages exported from the same TB folder > can exist in the same MBA mailbox! -- ________________________________________________________ Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Latest Vers: 1.53d FAQ : http://faq.thebat.dutaint.com