Need Outlook Express Help

W

wei

What a mess. Before I stop using OE, and forget I ever heard of it,
maybe someone can advise......

My OE is hopelessly hung. When I start it up, it displays the inbox
and highlights the first email therein, but then hangs forever. Delete
task is required to get out of there.

I am using XP SP3. I thought I was using OE v6, but when I try to
re-install a V6 I freshly downloaded, I get an error message that
there already is a higher-version OE on my system (oh???). I had the
thought that a complete re-install might get me going again (I thought
I could import the old mailboxes, that I have saved in an image
backup).

I notice that ControlPanel>Remove Programs does not even show OE. So
I can't do that. I went to Windows Explorer>Program Files to delete
OE manually from there, but I can't do that because it says OE is in
use (which it is not). I can't even do that in Safe Mode.

Again, I feel hopeless here. Anyone?

XieXie
Wei
 
C

Char Jackson

What a mess. Before I stop using OE, and forget I ever heard of it,
maybe someone can advise......

I've never been a fan of OE, so if you stopped using it you wouldn't
be hurting my feelings.
My OE is hopelessly hung. When I start it up, it displays the inbox
and highlights the first email therein, but then hangs forever. Delete
task is required to get out of there.

I'm guessing you have a corrupted Inbox. There are a couple of
solutions here:
<http://www.codeconscious.com/outlook-express/corrupted-oe-inbox.html>
 
S

Stefan Blom

Note that Outlook Express is part of *Windows* (XP was the last version to
include it), so you will have to uninstall it as you would any Windows
component. But the suggestion made by Char Jackson does sound promising.
 
W

wei

I've never been a fan of OE, so if you stopped using it you wouldn't
be hurting my feelings.


I'm guessing you have a corrupted Inbox. There are a couple of
solutions here:
<http://www.codeconscious.com/outlook-express/corrupted-oe-inbox.html>


I agree. I am about done trying to make this OE work. I even moved
ALL the dbx mailboxes from the only Identities folder I have to
something called c:\oemailboxes, leaving all former OE mailboxes gone
as far as I am concerned. OE still hangs, and displays the same
probably bad inbox. I even double-checked by searching for inbox.dbx
using windows explorer. Only found the one I had moved. Go figger.

Wei
 
V

VanguardLH

Stefan said:
Note that Outlook Express is part of *Windows* (XP was the last version to
include it), so you will have to uninstall it as you would any Windows
component. But the suggestion made by Char Jackson does sound promising.

Not correct. Outlook Express was bundled with Internet Explorer. To
get a later version of OE meant you installed a later version of IE.
Microsoft stopped bundling OE with IE as of IE7, and later, and why
version 6 of OE is the latest version of OE that you can get because IE6
was the last version in which OE was bundled.
 
V

VanguardLH

wei said:
What a mess. Before I stop using OE, and forget I ever heard of it,
maybe someone can advise......
<snipped the rest of the off-topic post>

Outlook and Outlook EXPRESS are two different programs. One is not the
big brother of the other, or one the light version of the other. They
are unrelated products. Outlook isn't related to Outlook EXPRESS isn't
related to Mozilla Thunderbird isn't related to Pegasus Mail and so on.

For help on Outlook EXPRESS, visit that newsgroup, which is:
microsoft.public.outlookexpress.general
 
W

wei

I agree. I am about done trying to make this OE work. I even moved
ALL the dbx mailboxes from the only Identities folder I have to
something called c:\oemailboxes, leaving all former OE mailboxes gone
as far as I am concerned. OE still hangs, and displays the same
probably bad inbox. I even double-checked by searching for inbox.dbx
using windows explorer. Only found the one I had moved. Go figger.

Wei

This AM, went one step further - I ERASED the entire IDENTITIES
FOLDER! Now OE should have no mailboxes, right? Well, guess what?
When OE starts it shows the SAME inbox, and still hangs up.
I give up.

Wei
 
V

VanguardLH

wei said:
This AM, went one step further - I ERASED the entire IDENTITIES
FOLDER! Now OE should have no mailboxes, right? Well, guess what?
When OE starts it shows the SAME inbox, and still hangs up. I give
up.

If the .dbx files are missing then OE recreates them when it loads.
That doesn't populate them with any records but just creates the
database files. When you started OE, I bet you were not disconnected
from the Internet, so OE dutifully performed its mail poll as you
configured it to do, downloaded all the e-mails again from the server
(since they all look new/unread to OE since e-mail clients track that
and not the server), and your Inbox got repopulated because it polled
your account to add records to the new .dbx files you had OE create when
it started.

Disconnect from the Internet. Turn off the router, yank the RJ45 from
your computer's port or to where it goes to the router, or right-click
on the connectoid in the Network applet in Control Panel and select
disconnect (disable). Then exit OE and delete the .dbx files. Then
load OE which will recreate the .dbx files. Because you are
disconnected from the Internet, OE cannot poll your e-mail account on
the server. At that point, is OE working okay?

If OE "hangs up" when you connect your host to the Internet so OE can
poll your e-mail account then you could have issues with software
outside of OE or with the mail server to which OE connects. It is
possible an e-mail is corrupted up on the mail server. It simply
doesn't know when the message ends or fails to read the file for it so
it never sends the dot-delimiter line. Your e-mail client is going to
send a RETR[ieve] command after which the server is supposed to send a
DATA command (to mark that it is going to send the message) followed by
the headers and body of the message followed by a dot-delimiter line (a
dot or period character in position 1 of the line followed by a newline
so that the entire line is just the period character). The
dot-delimiter tells the client that the server is done transmitting the
message to the client. To test if this is the cause (of a corrupted
e-mail up on the server), use the webmail client to access your e-mail
client. Then move out ALL message from the Inbox folder. Stick them in
another user-defined folder or read them and delete them. Then load OE
and see if it now works okay when your mailbox is empty up on the
server.

If that doesn't fix your problem, determine what software you installed
on your host that interrogates your e-mail traffic. One usual suspect
is anti-virus (AV) software. Some work as transparent proxies that
inspect the e-mail traffic on-the-fly. As the server sends the bytes
after the DATA command, the AV proxy looks at them a few at a time and
then passes them onto your e-mail client. That way, your e-mail client
doesn't timeout waiting for the message to arrive from the server. Of
course, if the AV proxy is farked then it won't be delivering the e-mail
traffic from the server to your client. I've seen that happen in
Norton's AntiVirus product when its transparent proxy went brain dead
and requires reloading the services and background processes (in the
proper order) to get their proxy working again; however, unless you have
batch files to do the stop and restart of their services and processes,
it's easier to just reboot your host to get their proxy working again.

Some AV programs pretend to be both the client and the server. When
your e-mail client sends an e-mail, their AV proxy grabs the whole
message by pretending it is the mail server. Your client is really
sending e-mails to the AV inspector instead of to the real mail server.
After the AV inspector gets done interrogating the entire message then
it pretends it is the client and connects to the mail server to send it
your message. Likewise, on receiving e-mails, the AV inspector pretends
it is the client and retrieves the entire e-mail (your e-mail client
doesn't have anything of it yet). The AV inspector interrogates the
content of the e-mail looking for malware. When it is happy then it
pretends to be the server and passes the e-mail down to your real e-mail
client. The delay of when the real e-mail client sent a RETR command,
the AV inspector sending it to the real e-mail server, the server
sending the DATA command, message, and dot-delimiter to the AV
inspector, the AV inspector to inspect the e-mail, and finally for the
AV inspector to actually deliver it to your e-mail client can take so
long that your e-mail client timesout (but before the timout it hangs
there waiting). "Hangs forever" doesn't say how long you waited. I
don't remember what is the timeout setting in OE (the one that is there
is for the handshaking to establish a connection and mail session, not
how long to wait during a DATA transfer). I suspect it is 5 minutes
(the same time IE waits before timing out for a non-responsive site).
So how long did you wait while OE was hung before determining it was
likely hung forever?

Interrogation of e-mails looking for malware is superfluous as it adds
no additional protection against any attached malware in the e-mails.
The same engine that is scanning your e-mails is the same one used to
scan the files that you create when you extract attachments to save them
as files (whether you save them separately as files you use later or
save them temporarily by using an "open" function in the e-mail client).
Often to resolve e-mail client problems means disabling e-mail scanning
by the AV program and retest.

If you deleted the .dbx files and started OE when you had *no* Internet
access and OE hung then we know there is a problem within OE. If OE
works okay when loaded and recreating new .dbx files when you do *not*
have Internet access then the problem is outside of OE, like corrupted
e-mails up on the server or security software interferring with OE.
 
W

wei

If the .dbx files are missing then OE recreates them when it loads.
That doesn't populate them with any records but just creates the
database files. When you started OE, I bet you were not disconnected
from the Internet, so OE dutifully performed its mail poll as you
configured it to do, downloaded all the e-mails again from the server
(since they all look new/unread to OE since e-mail clients track that
and not the server), and your Inbox got repopulated because it polled
your account to add records to the new .dbx files you had OE create when
it started.

Thanks for the voluminous, informative reply. You are right - I was
connected to the web during my trials, and yes my Verizon webmail
indeed has retained the e-mails and so would have reloaded them.
However, I have switched off Internet, erased the Identities folder
completely, and started OE. I get same inbox of emails and OE still
hangs there with the first e-mail highlighted - which I suspect may be
a problem?
I am going to go to my webmail and see if I can find said e-mail and
remove it from there to see what happens then. Let ya know

Wei
Disconnect from the Internet. Turn off the router, yank the RJ45 from
your computer's port or to where it goes to the router, or right-click
on the connectoid in the Network applet in Control Panel and select
disconnect (disable). Then exit OE and delete the .dbx files. Then
load OE which will recreate the .dbx files. Because you are
disconnected from the Internet, OE cannot poll your e-mail account on
the server. At that point, is OE working okay?

If OE "hangs up" when you connect your host to the Internet so OE can
poll your e-mail account then you could have issues with software
outside of OE or with the mail server to which OE connects. It is
possible an e-mail is corrupted up on the mail server. It simply
doesn't know when the message ends or fails to read the file for it so
it never sends the dot-delimiter line. Your e-mail client is going to
send a RETR[ieve] command after which the server is supposed to send a
DATA command (to mark that it is going to send the message) followed by
the headers and body of the message followed by a dot-delimiter line (a
dot or period character in position 1 of the line followed by a newline
so that the entire line is just the period character). The
dot-delimiter tells the client that the server is done transmitting the
message to the client. To test if this is the cause (of a corrupted
e-mail up on the server), use the webmail client to access your e-mail
client. Then move out ALL message from the Inbox folder. Stick them in
another user-defined folder or read them and delete them. Then load OE
and see if it now works okay when your mailbox is empty up on the
server.

If that doesn't fix your problem, determine what software you installed
on your host that interrogates your e-mail traffic. One usual suspect
is anti-virus (AV) software. Some work as transparent proxies that
inspect the e-mail traffic on-the-fly. As the server sends the bytes
after the DATA command, the AV proxy looks at them a few at a time and
then passes them onto your e-mail client. That way, your e-mail client
doesn't timeout waiting for the message to arrive from the server. Of
course, if the AV proxy is farked then it won't be delivering the e-mail
traffic from the server to your client. I've seen that happen in
Norton's AntiVirus product when its transparent proxy went brain dead
and requires reloading the services and background processes (in the
proper order) to get their proxy working again; however, unless you have
batch files to do the stop and restart of their services and processes,
it's easier to just reboot your host to get their proxy working again.

Some AV programs pretend to be both the client and the server. When
your e-mail client sends an e-mail, their AV proxy grabs the whole
message by pretending it is the mail server. Your client is really
sending e-mails to the AV inspector instead of to the real mail server.
After the AV inspector gets done interrogating the entire message then
it pretends it is the client and connects to the mail server to send it
your message. Likewise, on receiving e-mails, the AV inspector pretends
it is the client and retrieves the entire e-mail (your e-mail client
doesn't have anything of it yet). The AV inspector interrogates the
content of the e-mail looking for malware. When it is happy then it
pretends to be the server and passes the e-mail down to your real e-mail
client. The delay of when the real e-mail client sent a RETR command,
the AV inspector sending it to the real e-mail server, the server
sending the DATA command, message, and dot-delimiter to the AV
inspector, the AV inspector to inspect the e-mail, and finally for the
AV inspector to actually deliver it to your e-mail client can take so
long that your e-mail client timesout (but before the timout it hangs
there waiting). "Hangs forever" doesn't say how long you waited. I
don't remember what is the timeout setting in OE (the one that is there
is for the handshaking to establish a connection and mail session, not
how long to wait during a DATA transfer). I suspect it is 5 minutes
(the same time IE waits before timing out for a non-responsive site).
So how long did you wait while OE was hung before determining it was
likely hung forever?

Interrogation of e-mails looking for malware is superfluous as it adds
no additional protection against any attached malware in the e-mails.
The same engine that is scanning your e-mails is the same one used to
scan the files that you create when you extract attachments to save them
as files (whether you save them separately as files you use later or
save them temporarily by using an "open" function in the e-mail client).
Often to resolve e-mail client problems means disabling e-mail scanning
by the AV program and retest.

If you deleted the .dbx files and started OE when you had *no* Internet
access and OE hung then we know there is a problem within OE. If OE
works okay when loaded and recreating new .dbx files when you do *not*
have Internet access then the problem is outside of OE, like corrupted
e-mails up on the server or security software interferring with OE.
 
W

wei

If the .dbx files are missing then OE recreates them when it loads.
That doesn't populate them with any records but just creates the
database files. When you started OE, I bet you were not disconnected
from the Internet, so OE dutifully performed its mail poll as you
configured it to do, downloaded all the e-mails again from the server
(since they all look new/unread to OE since e-mail clients track that
and not the server), and your Inbox got repopulated because it polled
your account to add records to the new .dbx files you had OE create when
it started.

Disconnect from the Internet. Turn off the router, yank the RJ45 from
your computer's port or to where it goes to the router, or right-click
on the connectoid in the Network applet in Control Panel and select
disconnect (disable). Then exit OE and delete the .dbx files. Then
load OE which will recreate the .dbx files. Because you are
disconnected from the Internet, OE cannot poll your e-mail account on
the server. At that point, is OE working okay?

Nope, that wasn't it. The hanging email (if that is the culprit) is
not in my webmail. It is dated back in May. In fact there are five
others in the webmail inbox dated in May and none of them are being
downloaded. Next I am going to completely clear my webmail inbox of
all emails before July to see effect.

Wei
If OE "hangs up" when you connect your host to the Internet so OE can
poll your e-mail account then you could have issues with software
outside of OE or with the mail server to which OE connects. It is
possible an e-mail is corrupted up on the mail server. It simply
doesn't know when the message ends or fails to read the file for it so
it never sends the dot-delimiter line. Your e-mail client is going to
send a RETR[ieve] command after which the server is supposed to send a
DATA command (to mark that it is going to send the message) followed by
the headers and body of the message followed by a dot-delimiter line (a
dot or period character in position 1 of the line followed by a newline
so that the entire line is just the period character). The
dot-delimiter tells the client that the server is done transmitting the
message to the client. To test if this is the cause (of a corrupted
e-mail up on the server), use the webmail client to access your e-mail
client. Then move out ALL message from the Inbox folder. Stick them in
another user-defined folder or read them and delete them. Then load OE
and see if it now works okay when your mailbox is empty up on the
server.

If that doesn't fix your problem, determine what software you installed
on your host that interrogates your e-mail traffic. One usual suspect
is anti-virus (AV) software. Some work as transparent proxies that
inspect the e-mail traffic on-the-fly. As the server sends the bytes
after the DATA command, the AV proxy looks at them a few at a time and
then passes them onto your e-mail client. That way, your e-mail client
doesn't timeout waiting for the message to arrive from the server. Of
course, if the AV proxy is farked then it won't be delivering the e-mail
traffic from the server to your client. I've seen that happen in
Norton's AntiVirus product when its transparent proxy went brain dead
and requires reloading the services and background processes (in the
proper order) to get their proxy working again; however, unless you have
batch files to do the stop and restart of their services and processes,
it's easier to just reboot your host to get their proxy working again.

Some AV programs pretend to be both the client and the server. When
your e-mail client sends an e-mail, their AV proxy grabs the whole
message by pretending it is the mail server. Your client is really
sending e-mails to the AV inspector instead of to the real mail server.
After the AV inspector gets done interrogating the entire message then
it pretends it is the client and connects to the mail server to send it
your message. Likewise, on receiving e-mails, the AV inspector pretends
it is the client and retrieves the entire e-mail (your e-mail client
doesn't have anything of it yet). The AV inspector interrogates the
content of the e-mail looking for malware. When it is happy then it
pretends to be the server and passes the e-mail down to your real e-mail
client. The delay of when the real e-mail client sent a RETR command,
the AV inspector sending it to the real e-mail server, the server
sending the DATA command, message, and dot-delimiter to the AV
inspector, the AV inspector to inspect the e-mail, and finally for the
AV inspector to actually deliver it to your e-mail client can take so
long that your e-mail client timesout (but before the timout it hangs
there waiting). "Hangs forever" doesn't say how long you waited. I
don't remember what is the timeout setting in OE (the one that is there
is for the handshaking to establish a connection and mail session, not
how long to wait during a DATA transfer). I suspect it is 5 minutes
(the same time IE waits before timing out for a non-responsive site).
So how long did you wait while OE was hung before determining it was
likely hung forever?

Interrogation of e-mails looking for malware is superfluous as it adds
no additional protection against any attached malware in the e-mails.
The same engine that is scanning your e-mails is the same one used to
scan the files that you create when you extract attachments to save them
as files (whether you save them separately as files you use later or
save them temporarily by using an "open" function in the e-mail client).
Often to resolve e-mail client problems means disabling e-mail scanning
by the AV program and retest.

If you deleted the .dbx files and started OE when you had *no* Internet
access and OE hung then we know there is a problem within OE. If OE
works okay when loaded and recreating new .dbx files when you do *not*
have Internet access then the problem is outside of OE, like corrupted
e-mails up on the server or security software interferring with OE.
 
W

wei

Well - I erased all emails from all webmail mailboxes.
OE still begins with same inbox display and acts the same -
IE it is hung until I kill it. I guess that means my problem is
within OE, huh?

Wei




If the .dbx files are missing then OE recreates them when it loads.
That doesn't populate them with any records but just creates the
database files. When you started OE, I bet you were not disconnected
from the Internet, so OE dutifully performed its mail poll as you
configured it to do, downloaded all the e-mails again from the server
(since they all look new/unread to OE since e-mail clients track that
and not the server), and your Inbox got repopulated because it polled
your account to add records to the new .dbx files you had OE create when
it started.

Disconnect from the Internet. Turn off the router, yank the RJ45 from
your computer's port or to where it goes to the router, or right-click
on the connectoid in the Network applet in Control Panel and select
disconnect (disable). Then exit OE and delete the .dbx files. Then
load OE which will recreate the .dbx files. Because you are
disconnected from the Internet, OE cannot poll your e-mail account on
the server. At that point, is OE working okay?

If OE "hangs up" when you connect your host to the Internet so OE can
poll your e-mail account then you could have issues with software
outside of OE or with the mail server to which OE connects. It is
possible an e-mail is corrupted up on the mail server. It simply
doesn't know when the message ends or fails to read the file for it so
it never sends the dot-delimiter line. Your e-mail client is going to
send a RETR[ieve] command after which the server is supposed to send a
DATA command (to mark that it is going to send the message) followed by
the headers and body of the message followed by a dot-delimiter line (a
dot or period character in position 1 of the line followed by a newline
so that the entire line is just the period character). The
dot-delimiter tells the client that the server is done transmitting the
message to the client. To test if this is the cause (of a corrupted
e-mail up on the server), use the webmail client to access your e-mail
client. Then move out ALL message from the Inbox folder. Stick them in
another user-defined folder or read them and delete them. Then load OE
and see if it now works okay when your mailbox is empty up on the
server.

If that doesn't fix your problem, determine what software you installed
on your host that interrogates your e-mail traffic. One usual suspect
is anti-virus (AV) software. Some work as transparent proxies that
inspect the e-mail traffic on-the-fly. As the server sends the bytes
after the DATA command, the AV proxy looks at them a few at a time and
then passes them onto your e-mail client. That way, your e-mail client
doesn't timeout waiting for the message to arrive from the server. Of
course, if the AV proxy is farked then it won't be delivering the e-mail
traffic from the server to your client. I've seen that happen in
Norton's AntiVirus product when its transparent proxy went brain dead
and requires reloading the services and background processes (in the
proper order) to get their proxy working again; however, unless you have
batch files to do the stop and restart of their services and processes,
it's easier to just reboot your host to get their proxy working again.

Some AV programs pretend to be both the client and the server. When
your e-mail client sends an e-mail, their AV proxy grabs the whole
message by pretending it is the mail server. Your client is really
sending e-mails to the AV inspector instead of to the real mail server.
After the AV inspector gets done interrogating the entire message then
it pretends it is the client and connects to the mail server to send it
your message. Likewise, on receiving e-mails, the AV inspector pretends
it is the client and retrieves the entire e-mail (your e-mail client
doesn't have anything of it yet). The AV inspector interrogates the
content of the e-mail looking for malware. When it is happy then it
pretends to be the server and passes the e-mail down to your real e-mail
client. The delay of when the real e-mail client sent a RETR command,
the AV inspector sending it to the real e-mail server, the server
sending the DATA command, message, and dot-delimiter to the AV
inspector, the AV inspector to inspect the e-mail, and finally for the
AV inspector to actually deliver it to your e-mail client can take so
long that your e-mail client timesout (but before the timout it hangs
there waiting). "Hangs forever" doesn't say how long you waited. I
don't remember what is the timeout setting in OE (the one that is there
is for the handshaking to establish a connection and mail session, not
how long to wait during a DATA transfer). I suspect it is 5 minutes
(the same time IE waits before timing out for a non-responsive site).
So how long did you wait while OE was hung before determining it was
likely hung forever?

Interrogation of e-mails looking for malware is superfluous as it adds
no additional protection against any attached malware in the e-mails.
The same engine that is scanning your e-mails is the same one used to
scan the files that you create when you extract attachments to save them
as files (whether you save them separately as files you use later or
save them temporarily by using an "open" function in the e-mail client).
Often to resolve e-mail client problems means disabling e-mail scanning
by the AV program and retest.

If you deleted the .dbx files and started OE when you had *no* Internet
access and OE hung then we know there is a problem within OE. If OE
works okay when loaded and recreating new .dbx files when you do *not*
have Internet access then the problem is outside of OE, like corrupted
e-mails up on the server or security software interferring with OE.
 
C

Char Jackson

Thanks for the voluminous, informative reply. You are right - I was
connected to the web during my trials, and yes my Verizon webmail
indeed has retained the e-mails and so would have reloaded them.
However, I have switched off Internet, erased the Identities folder
completely, and started OE. I get same inbox of emails and OE still
hangs there with the first e-mail highlighted - which I suspect may be
a problem?
I am going to go to my webmail and see if I can find said e-mail and
remove it from there to see what happens then. Let ya know

If you're deleting the .dbx files, then you launch OE and it still
shows your old email, it probably means you're deleting the wrong set
of .dbx files. Deleting or renaming Inbox.dbx should result in a clean
Inbox, not counting the boilerplate Welcome message. Are you
absolutely sure you're working with the right set of .dbx files?
 
W

wei

If you're deleting the .dbx files, then you launch OE and it still
shows your old email, it probably means you're deleting the wrong set
of .dbx files. Deleting or renaming Inbox.dbx should result in a clean
Inbox, not counting the boilerplate Welcome message. Are you
absolutely sure you're working with the right set of .dbx files?


Well I thought I was. I again used Windows Explorer to search for
*.dbx files, and I deleted everyone found. But this time when I
restarted OE, the bad emails are gone and the inbox is refreshed with
a few new emails, and OE is functioning okay so far.

Thanks for the insights.

Wei
 
C

Char Jackson

Well I thought I was. I again used Windows Explorer to search for
*.dbx files, and I deleted everyone found. But this time when I
restarted OE, the bad emails are gone and the inbox is refreshed with
a few new emails, and OE is functioning okay so far.

Thanks for the insights.

Woohoo! I hope it's fixed for good.
 
W

wei

Woohoo! I hope it's fixed for good.


Yeh - As I said, I was ready to scrap OE. No idea what hung it up in
the first place. Never will. But I shud have caught on how to fix it
earlier.
My bad.
XieXie
Wei
 
V

VanguardLH

wei said:
Well I thought I was. I again used Windows Explorer to search for
*.dbx files, and I deleted everyone found. But this time when I
restarted OE, the bad emails are gone and the inbox is refreshed with
a few new emails, and OE is functioning okay so far.

To find out where OE is saving its database (.dbx) files, go look at
its maintenance options: Tools -> Options -> Maintenance -> Store
Folder.

If you were deleting all .dbx files found on your computer, you
probably have deleted database files for some other application. DBX
filetypes are used by other applications, like Databeam Image, Visual
Foxpro, Formula Graphics Project, and others. Any app can use whatever
filetype it wants for its config or data files.
 
W

wei

To find out where OE is saving its database (.dbx) files, go look at
its maintenance options: Tools -> Options -> Maintenance -> Store
Folder.

If you were deleting all .dbx files found on your computer, you
probably have deleted database files for some other application. DBX
filetypes are used by other applications, like Databeam Image, Visual
Foxpro, Formula Graphics Project, and others. Any app can use whatever
filetype it wants for its config or data files.

I agree. In fact I saw a few dbx files that appeared not to be OE
mailbox related because their location and parentage indicated
otherwise. Ergo, I tried to be smart enough to leave them alone.
So I should be all right there.

XieXie
Wei
 
D

Don Schmidt

OE doesn't list in Add/Remove Programs in the default area, "Change or
Remove Programs". Look in the third listing down in the left column,
"Add/Remove Windows Components".

Good luck,
 
S

Stefan Blom

Actually, we are both correct. Outlook Express was a Windows component and
bundled with Internet Explorer.

But the point in this thread is that questions on OE are off-topic in an Outlook
thread.

--
Stefan Blom
Microsoft Word MVP
 
V

VanguardLH

Stefan said:
But the point in this thread is that questions on OE are off-topic in an Outlook
thread.

I mentioned that 2 days ago but Char and I decided to help here, anyway.
The OP got OE working again.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top