"Brett" wrote in message
...
Nothing showed in OE in the folder in question after the limit was hit.
The dbx was 2,097,000 bytes in size. Throwing it in a hex editor showed
the data was still there. I assume the file has an integer index in it
that overflows at 2 gig.

I found a tool with source that reads dbx's and dumps them to mbox format.
It also saw no messages. I then modified it to to use unsigned integers
rather than signed in order to double the number of ints available
(assuming the integer overflow) but also no luck. Was not worth spending
more time on this tract, so I purchased DBXpress, and 4 hours later had
12,000 + .msg files, which I was able to import into smaller folders.
The customer was happy, but I was very preturbed at the lack of robustness
displayed by the dbx format.

Needless to say, MS should have a corrupt dbx recovery tool.

Its called DBXpress. G I'd be happy to sell them the exclusive
distributions rights for only 10 cents per Windows user. VBG

From what I have read the dbx structure is complete crap, and the people
that designed and approved the design should be taken out and be whipped,
kicked, beaten, strangled, stabbed, shot, then fed to rats, and then the
rats need to be shot.


This has already happened. Unfortunately the important part -- fixing the
actual problem -- hasn't yet occured. And won't until Vista.

I know more about the dbx file structure than anybody, but unfortunately
knowledge can come at a high price.

cheers,

steve




"Bruce Hagen" wrote in message
...
Did you lose messages? What exactly happened?
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Brett" wrote in message
...
Just found out about the 2 gig limit on dbx files, the hard way. Is
there an easy quick way to work arround this problem?