Using a User Defined Function as a constraint within a temporary table.

Question

Hello, 
I am trying to create a temp table that uses a UDF in a constraint. I'm getting the following error message 
Msg 4121, Level 16, State 1, Line 1
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.CK_LoseTeamSportExists", or the name is ambiguous.
I've tested the function and it works in other contexts. Any idea? All code below:  
Thanks, 
- Bryon
create function dbo.CK_LoseTeamSportExists (@loseteam int, @sportid int)
returns bit
as
begin
declare @return bit
if exists 
select TeamID, sportid from Link_TeamSport
where 
TeamID = @loseteam 
and
SportID = @sportid
set @return = 1
else set @return = 0
return @return
end
go
create table #check
SportID int
,WinTeamID int
,LoseTeamID int
,check 
(dbo.CK_LoseTeamSportExists(LoseTeamID,SportID) = 1)

Answer 1

Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, data types, etc. in your schema are. Learn how to follow ISO-11179 data element naming conventions and formatting rules. Temporal data should
use ISO-8601 formats. Code should be in Standard SQL as much as possible and not local dialect. 
This is minimal polite behavior on SQL forums. 
>> I am trying to create a temp table that uses a UDF in a constraint. <<
You do not understand how SQL or any declarative language works! 
We do not use UDFs (procedural programming)
We do not use bit flags (assembly language).
We do not use temp tables (mag tape files).
We do not use integer as identifiers (what math do you do on them?)
Your silly “Link_TeamSport” implies a pointer chain; we have no links in SQL. Where is the DDL? 
Constraints are always predicates in any declarative language. 
Do you know why you have to create a local variable to pass the non-relational flag back to the calling environment? FORTRAN I and II! These early languages has to use hardware registers in the first IBM computers to return results. In your ignorance, you mimic
them! 
We do not use if-then-else control flow in any declarative language. We have CASE expressions that we put where you have a local variable getting an assignment. 
I see you also put the comma at the start of the line. We did that with punch cards, so we could re-use them 50 years ago. 
In SQL, we would use REFERENCES to assure a team reference exists. We use names for teams because they are entities, not quantities: 
CREATE TABLE Game_Results
(sport_name CHAR(10) NOT NULL PRIMARY KEY,
 win_team_name CHAR(12) NOT NULL
  REFERENCES Teams(team_name)
   ON DELETE CASCADE,
 lose_team_name CHAR(12) NOT NULL
  REFERENCES Teams(team_name)
   ON DELETE CASCADE,
 CHECK (win_team_name <> lose_team_name)); 
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL