James Trudeau <[log in to unmask]> writes: >Howdy, >Last week we had an application fail with dreaded "Broken Chain" message. >To keep it short: it wasn't really a broken chain. With a bunch of help >from Adager we found that there were 2,305 records missing from the dataset. >Further investigation turned up 52 blocks of hosed (technical term for >set to binary zeros) records beginning on an even block boundry near the >end of the records in the set. The suspect is DDX. Yikes! Just when I figured that DDX was "ready for prime time", this comes up! I was seriously considering enabling DDX for some datasets, but with stories like this, how can I? Does anyone have any more info on this? I knew that DDX had a problem when it was first introduced (something about over-writing data in other files IIRC), but this is the first I've heard of this. Jim Phillips Manager of Information Systems E-Mail: [log in to unmask] Therm-O-Link, Inc. Phone: (330) 527-2124 P. O. Box 285 Fax: (330) 527-2123 Garrettsville, Ohio 44231