TB! and Windows Explorer

2001-10-31 Thread Carren
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! I have been having major frustrations with archiving some of my mail folders with Mailbag Assistant. I think I finally have it figured out, but it has brought to light an interesting discovery and I am interested in your opinions. It would

Re: TB! and Windows Explorer

2001-10-31 Thread Allie C Martin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @ 09:57:51 +1300 [ Thu, 1 Nov 2001], Carren [C] contributed this to our collective wisdom: ... C It would appear, after much tearing out of hair, that Windows C Explorer has not been updating it's TB! information according to C changes I have made

Re: TB! and Windows Explorer

2001-10-31 Thread Allie C Martin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @ 16:20:21 -0600 [ Wed, 31 Oct 2001], Dwight A Corrin [DAC] wrote these words of wisdom: ... For me, I've noted that TB! will not rename account folders when you rename the accounts via the TB! interface. However, I've been making a lot of changes

Re: TB! and Windows Explorer

2001-10-31 Thread Dwight A Corrin
On Wednesday, October 31, 2001, 4:02:21 PM, Allie C Martin wrote: For me, I've noted that TB! will not rename account folders when you rename the accounts via the TB! interface. However, I've been making a lot of changes *within* accounts for the last couple weeks and all folder names and

Re[2]: TB! and Windows Explorer

2001-10-31 Thread Carren
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thursday, November 01, 2001, 11:02:21 AM, Allie wrote: ACM But hold on. If you move folders around in TB!, it *will* break ACM any shortcuts that you may have created in Mailbag Assistant, ACM since the shortcuts are pointing to the folders

Re[2]: TB! and Windows Explorer

2001-10-31 Thread Carren
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thursday, November 01, 2001, 11:02:21 AM, Allie wrote: ACM TB! seems to keep up here at my end. If the changes aren't being ACM reflected in Explorer then it's TB!'s fault. Just as an after thought. One of my accounts currently has *no*