Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Error???

Author  Topic 

kamalkishore_in
Yak Posting Veteran

76 Posts

Posted - 2002-04-07 : 23:26:59
Hi guys,
I am getting the following error...

SqlDumpExceptionHandler:
c0000005 EXCEPTION_ACCESS_VIOLATION

IN ONE SQL SERVER THE STATEMENT IS WORKING FINE, BUT SAME STATEMENT IS GIVING THE ABOVE ERROR.

THE STATEMENT IS

INSERT INTO CHO_ALL_REPORT1 SELECT 0 as FG, 0 AS RANK1, 0 AS RANK2, 0 AS RANK3, ISNULL(ISNULL(A.CHO_SUPCD, B.CHO_SUPCD),C.CHO_SUPCD) AS CHO_SUPCD, ISNULL(ISNULL(A.CHO_SUPNM,B.CHO_SUPNM),C.CHO_SUPNM) AS CHO_SUPNM, ISNULL(A.MONTH1,0) AS MONTH1, ISNULL(A.MONTH2,0) AS MONTH2, ISNULL(B.YEAR1,0) AS YEAR1, ISNULL(B.YEAR2,0) AS YEAR2, ISNULL(C.PRE1,0) AS PRE1, ISNULL(C.PRE2,0) AS PRE2
From (SELECT LEFT(CHO_SUPCD,4) AS CHO_SUPCD, MAX(CHO_SUPNM) AS CHO_SUPNM, SUM(CHO_URITKIN) AS MONTH1, SUM(CHO_URITKIN - CHO_SHITKIN) As MONTH2 From COMP_CHOKUH_SUPCD
Where (Month(CHO_DENDATE) = 2 and year(CHO_DENDATE) = 2002 AND LEFT(CHO_HANCD,4) <> 9500) GROUP BY LEFT(CHO_SUPCD,4)) A
FULL OUTER JOIN (SELECT LEFT(CHO_SUPCD,4) AS CHO_SUPCD, MAX(CHO_SUPNM) AS CHO_SUPNM, SUM(CHO_URITKIN) AS YEAR1, SUM(CHO_URITKIN - CHO_SHITKIN) As YEAR2
From COMP_CHOKUH_SUPCD WHERE (CHO_DENDATE < '2002/03/01' AND CHO_DENDATE >= '2001/04/01' AND LEFT(CHO_HANCD,4) <> 9500) GROUP BY LEFT(CHO_SUPCD,4)) B
ON A.CHO_SUPCD = B.CHO_SUPCD FULL OUTER JOIN (SELECT LEFT(CHO_SUPCD,4) AS CHO_SUPCD, MAX(CHO_SUPNM) AS CHO_SUPNM, SUM(CHO_URITKIN) AS PRE1,
SUM(CHO_URITKIN - CHO_SHITKIN) As PRE2 From COMP_CHOKUH_SUPCD
WHERE (CHO_DENDATE < '2001/03/01' AND CHO_DENDATE >= '2000/04/01' AND LEFT(CHO_HANCD,4) <> 9500) GROUP BY LEFT(CHO_SUPCD,4)) C
ON A.CHO_SUPCD = C.CHO_SUPCD

NEED HELP...



Merkin
Funky Drop Bear Fearing SQL Dude!

4970 Posts

Posted - 2002-04-07 : 23:40:09
According to Chad, when you get errors like that, it is most likely a bug. Your best bet is to call Microsoft support and they will find a workaround for you.

Damian
Go to Top of Page
   

- Advertisement -