Correct - the Outlook contact list is empty. Or, was. Via OE, I added one
contact, shut down OE, and started Outlook, and found that one contact. (A
confirmation experiment).


"Michael Santovec" wrote in message
...
If the registry was set to share the contacts, then turn that setting off
(set the value to 0). That accidentally being turned on would cause OE to
ignore the WAB file and use the Outlook Contacts, which I presume are
empty.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"JoeSpareBedroom" wrote in message
...
Interesting registry change, but here's the issue: The ONLY reason I
started up Outlook was to assist a remote user. I needed to see what he's
seeing. After that's done, I won't be using it. I don't want OE to use
Outlook contacts since I will never be using Outlook. I want OE to access
its own WAB file in the old location.


"Michael Santovec" wrote in message
...
Outlook Express may be set to use the Outlook Contacts instead of it's
WAB file.

To share Contacts between Outlook and Outlook Express
http://www.slipstick.com/contacts/oeshare.htm


--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"JoeSpareBedroom" wrote in message
...
Well, not the .wab file, just the addresses in it. Fortunately, I do
backups daily. Here's what I *believe* is the reason for the vanishing
addresses - perhaps someone can confirm this: I use OE, *never*
Outlook. But, next week, I need to assist someone by phone with a
couple of setup processes in Outlook. So yesterday, I started Outlook
for the first time on this computer, figuring now I'll be able to see
the same menus they're looking at. I went along with its initial setup
questions, and figured "OK - I'm all set here".

For the rest of the day, I didn't access my address book at all, so I
didn't notice that it had been replaced by the Outlook installation.
Between now and next week, I may want to add an address or two (after I
restore the backed up file). Is Outlook going to wipe out that file
every time I start it up??? If yes, is there a way to avoid that?

Running XP Pro SP2, by the way.