Yes, ROUND() gets single numeric expression which represents single value according to the precision specified.

If you would read math handbook in school you'd know that rounding a value having 6...

ROUND() sees numeric representation a value between 0.045000(0) and 0.045000(9).

In case of 0.666666 ROUND() sees, according to the same logic, numeric representation for a value between 0.666666(0) and 0.666666(9).

According to...

My answer is "No, it does not".

Because datatype specified for the parameter has limited precision.

LIMITED PRECISION.

Absolutely precise value cannot be passed into the function.

Because all DECIMAL datatypes don't support absolutely...

Sorry, David,

but due to limited precision any computing system cannot pass exact representation for all values.

That's why all computing system use representations for actual non-precise valuers. Precision of the...

You did not succeed in any way with 5/111.111.

Result is incorrect.

And you cannot get correct result because the function does not work with imprecise values.

And every value is with 100%...

[dbo].[fn_BRound2] (-612.945, 2)

"If you cannot succeed change the requirements."

David, yes, ROUND gets the same value, but it takes into consideration that result of division presented with precise value is always <= actual result of division which is with...

This is the problem of the function.

This is the problem of the assumption it's based on.

You can pass only limited number of values to it and YOU CANNOT PASS TO...

The problem is

5/111.111 > 0.04500000000000000000

Welcome to the real world.

SELECT a1.field2 , a2.field2 , a3.field2 , a4.field2

FROM a AS a1

LEFT OUTER JOIN a AS a2

ON (.....) AND a2.field1 = val2

LEFT OUTER JOIN a AS a3

ON (.....) AND a3.field1...

Why "double precision" (why you guys are playing with this name, it's synonym of "float"!) is not acceptable see the link posted by David Jackson.

For decimal(38, 20) you did not...

OK, time and attendance matching.

Done it once, and it did not involve any temp tables at all.

You're trying to use procedural language approaches instead of set-based T-SQL way.

You don't need...

Hmmm...

Quite tricky.

Don't have even a clue how to get Eastern Time from GMT...

Need to be PhD to do this.

I claim that concept is crap and therefore there is no perfect implementation.

If thee would be perfect implementation you would post it.

Flooding topic by you with words instead of single...