RE: [Emerald] HELP! SQL Server Error: 8646

Ronnie Franklin ( (no email) )
Mon, 23 Oct 2000 22:34:18 -0500

I got an answer from one of the techs yesterday.. so yes they still
monitor.. but probably not this late!

I have had the same problem with a couple of corrupted records.. asked and
never got a real fix.. so here is my work around.

I start by doing a

Delete from Calls
where (calldate > yy/yy/yy 00:00:01 AM) and
where (calldate < xx/xx/xx 12:59:59 pm)

Then when it bombs out, I just keep moving the xx/xx/xx date backwards until
I get to where it completes... I usually move the date by 1/2 of what I am
trying to delete so I can narrow down faster..

Once you have found the time frame of the 1 or 2 records that are causing
the problem then just adjust the date and time to avoid those records.

Probably not the best way, but it does work!!



This is a user supported list. If you require assistance from IEA Software's
Support Engineers, please check out our Support resources at

For more information about this list (including removal) go to: