(Using OE6 with all updates etc in place.)

From time to time OE will create a second DBX file for a newsgroup that I'm
subscribed to which has the same newsgroup name but with the addition of
"(1)". What is the reason for this?

--
Bob
http://www.kanyak.com

That happens when OE runs into corruption or other problems with the DBX
file. It creates a new file. The one with the latest update date is
the one being used. The other can be deleted.

--

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


"Opinicus" wrote in message
...
(Using OE6 with all updates etc in place.)

From time to time OE will create a second DBX file for a newsgroup
that I'm subscribed to which has the same newsgroup name but with the
addition of "(1)". What is the reason for this?

--
Bob
http://www.kanyak.com

"Michael Santovec" wrote in message
...

"Opinicus" wrote ...

From time to time OE will create a second DBX file for a newsgroup
that I'm subscribed to which has the same newsgroup name but with the
addition of "(1)". What is the reason for this?

That happens when OE runs into corruption or other problems with the
DBX file. It creates a new file. The one with the latest update date
is the one being used. The other can be deleted.

It also happens when a file by that name already exists. For example,
when you unsubscribe from a newsgroup, the .dbx file for it is supposed
to get deleted but only when exiting Outlook Express. If OE crashes
then the .dbx file does not get deleted. Even when OE exits okay, it
doesn't always comply by deleting the .dbx file for the unsubscribed
group. The result is that you *tried* to unsubscribe but the .dbx file
still exists. The next time you [re]subscribe to that same newsgroup,
the old .dbx file is still there so the "(n)" postfix is added to the
filename since same-named files cannot exist within the same directory.

After unsubscribing from a group and after exiting OE, I check if the
..dbx file actually got deleted. If not, I delete it.

It can also happen if you subscribe to the same NG on two different servers.

steve

"Vanguard" wrote in message
...
"Michael Santovec" wrote in message
...

"Opinicus" wrote ...

From time to time OE will create a second DBX file for a newsgroup that
I'm subscribed to which has the same newsgroup name but with the
addition of "(1)". What is the reason for this?

That happens when OE runs into corruption or other problems with the DBX
file. It creates a new file. The one with the latest update date is the
one being used. The other can be deleted.

It also happens when a file by that name already exists. For example,
when you unsubscribe from a newsgroup, the .dbx file for it is supposed to
get deleted but only when exiting Outlook Express. If OE crashes then the
.dbx file does not get deleted. Even when OE exits okay, it doesn't
always comply by deleting the .dbx file for the unsubscribed group. The
result is that you *tried* to unsubscribe but the .dbx file still exists.
The next time you [re]subscribe to that same newsgroup, the old .dbx file
is still there so the "(n)" postfix is added to the filename since
same-named files cannot exist within the same directory.

After unsubscribing from a group and after exiting OE, I check if the .dbx
file actually got deleted. If not, I delete it.