Hey Remi and Anders... nice tag team you guys made!

Ummmm.... You might want to read up on what a "Table Alias" is... it'll make that code look a lot cleaner...

...forgot the divide example... you want THIS kind of crappy accuracy? Tell me which company you're writing this for so I can make sure I...

I sure would like to know why you think MONEY gives incorrect results... 4 decimal places isn't enough?  Maybe not for interest calcs and monthly payment calcs...

But David and...

If the CLR UDF's don't, firing "n" number of queries certainly may... especially when "n" number of queries are calling UDF's... sounds like lots and lots of RBAR (pronounce "ree-bar"...

What kind of error are you getting... you might also post your code so we can help more.  And, don't forget, you must have "SA" privs to use it.

... and, BEST, you need to identify how table A and table B relate to each other... what would the join columns be?

Ummm.... take the ORDER BY out of the view... you should do the order by in procs that reference the view, not in the view itself.

How 'bout the fact that BOL says "OFF" is the default?

Does SQL 2K5 WorkGroup have either BCP or OSQL?  The reason I ask is that the cursor method will take a comparitively very long time... for every line you write to...

Thought I'd add one... see "M3"...

select

  M1 = right(1000000+MyNumber,4) ,

  M2 = right('0000'+convert(varchar(20),MyNumber),4),

  M3 = REPLACE(STR(MyNumber,4),' ','0')

from

  (

  select MyNumber=1 union all

  select 10 union all

  select 44 union all

  select 7777 union all

  select 9999 union...

Yep... I missed that... thanks Michael...

Jeremy, you need to change your function to a scalar function that returns a DATETIME instead of a table... then it should work ok...

Personnally, the look and feel of SSC are both the best on the web I've seen.  I'd leave it alone so far as any look and feel goes...

But I would...

Don't need the WorkCalendar join anymore... you have the function...

 SELECT o.Order_Num,

        o.CustomerNumber,

        o.ItemNum,

        o.RequireDate,

        o.State,

        tt.PrepTime,

        dbo.CalcDate(o.RequireDate,-tt.PrepTime) AS RequiredShipDate

   FROM dbo.Order...

I'd have to say "No".  The default for this setting is "OFF".  The only risk is if there's some really poor code written for GUI's that doesn't ID the type...