(SQL2K SP3a standard on W2K)
Well, actually a little bit more than that. I have an SP that creates, manipulates, and drops a global temp table. When I try to put the SP in the database, I get
Server: Msg 2714, Level 16, State 1, Procedure gensp_GetShipmentDetail_new, Line 169
There is already an object named '##tmp_getshipmentdetail_tmp' in the database.
OK, so I should just issue a DROP TABLE, right? Now I get
Server: Msg 3701, Level 11, State 5, Line 1
Cannot drop the table '##tmp_getshipmentdetail_tmp', because it does not exist in the system catalog.
How can this be? I already tried the fix suggested in KB827448, to no avail. While this thread floats, I'm also calling PSS.
Anyone out there with the same problem and/or a fix?
TIA for your time and expertise.
Phil Hegedusich
Senior Programmer/Analyst
IIMAK
-----------
I'm not as think as you confused I am.
-----------
Flabbergasted (a.): Amazed at how much weight one has gained.
-----------
Oyster (n.): One who sprinkles their conversation with Yiddish expressions.
Well, actually a little bit more than that. I have an SP that creates, manipulates, and drops a global temp table. When I try to put the SP in the database, I get
Server: Msg 2714, Level 16, State 1, Procedure gensp_GetShipmentDetail_new, Line 169
There is already an object named '##tmp_getshipmentdetail_tmp' in the database.
OK, so I should just issue a DROP TABLE, right? Now I get
Server: Msg 3701, Level 11, State 5, Line 1
Cannot drop the table '##tmp_getshipmentdetail_tmp', because it does not exist in the system catalog.
How can this be? I already tried the fix suggested in KB827448, to no avail. While this thread floats, I'm also calling PSS.
Anyone out there with the same problem and/or a fix?
TIA for your time and expertise.
Phil Hegedusich
Senior Programmer/Analyst
IIMAK
-----------
I'm not as think as you confused I am.
-----------
Flabbergasted (a.): Amazed at how much weight one has gained.
-----------
Oyster (n.): One who sprinkles their conversation with Yiddish expressions.