XSL和XPATH问题匹配(XSL and XPATH issue match)

 只需在表达式中包含一个floor() 
 
-- -------------------------------------------------------------------
-- set-up some test data using a CTE:
WITH tst as ( SELECT 13.7 finlength UNION ALL SELECT 123 )
-- alternatively: generate a table [tst] with a single column [finlength] 
-- -------------------------------------------------------------------

SELECT CONVERT(VARCHAR(20),FLOOR(finlength / 12)) + '''' 
     + CONVERT(VARCHAR(20),finlength % 12)+'"' as FinishLen
FROM tst

-- results:
FinishLen
1'1.70"
10'3."
 
 这会将第一个（ft）值转换为整数，而第二个（in）仍将显示小数点后的所有数字。 
 
 UPDATE 
 
 当我从#tmp表中运行select时，我得到了与OP相同的错误。 我然后修改并最终得到这个： 
 
 它现在像地狱一样丑陋，但至少它现在有效 ，请参见此处SQL演示 ： 
 
create table #tst (finlength float);
INSERT INTO #tst VALUES (13.7),(123.),(300.9);

SELECT CONVERT(VARCHAR(20),FLOOR(finlength / 12)) + '''' -- ft
      +CONVERT(VARCHAR(20),finlength-FLOOR(finlength)    -- in: fractional part
      +CAST(FLOOR(finlength) as int) %12)+'"'            -- in: integer part
as FinishLen 
FROM #tst
 
 请注意：公式将返回正值的合理结果。 对于“负距离”，需要进一步改变。 如果在不同的地方需要类似的输出，那么UDF在这里是有意义的。 就像是： 
 
CREATE FUNCTION ftinstr(@v float) RETURNS varchar(32) BEGIN
 DECLARE @l int;
 SELECT @l=FLOOR(ABS(@v));
 RETURN CAST(SIGN(@v)*(@l/12) AS varchar(6))+''''
       +CAST( ABS(@v)-@l+@l%12 AS varchar(20))+'"'
END
 
 会做的伎俩，被称为dbo.ftinstr( floatval ) 。 
 
 也许我还能把它美化一下...... 

Just include a floor() in your expression like
 
-- -------------------------------------------------------------------
-- set-up some test data using a CTE:
WITH tst as ( SELECT 13.7 finlength UNION ALL SELECT 123 )
-- alternatively: generate a table [tst] with a single column [finlength] 
-- -------------------------------------------------------------------

SELECT CONVERT(VARCHAR(20),FLOOR(finlength / 12)) + '''' 
     + CONVERT(VARCHAR(20),finlength % 12)+'"' as FinishLen
FROM tst

-- results:
FinishLen
1'1.70"
10'3."
 
This will turn the first (ft) value into an integer while the second one (in) will still show all the digits after the decimal point.
 
UPDATE
 
When I ran the select from a #tmp table I got the same error as OP. I then modified and ended up with this:
 
It is as ugly as hell now, but at least it works now, see here SQL Demo:
 
create table #tst (finlength float);
INSERT INTO #tst VALUES (13.7),(123.),(300.9);

SELECT CONVERT(VARCHAR(20),FLOOR(finlength / 12)) + '''' -- ft
      +CONVERT(VARCHAR(20),finlength-FLOOR(finlength)    -- in: fractional part
      +CAST(FLOOR(finlength) as int) %12)+'"'            -- in: integer part
as FinishLen 
FROM #tst
 
Please note: The formula will return reasonable results for positive values. For "negative distances" further changes are necessary. If similar output is required in different places then a UDF makes sense here. Something like: 
 
CREATE FUNCTION ftinstr(@v float) RETURNS varchar(32) BEGIN
 DECLARE @l int;
 SELECT @l=FLOOR(ABS(@v));
 RETURN CAST(SIGN(@v)*(@l/12) AS varchar(6))+''''
       +CAST( ABS(@v)-@l+@l%12 AS varchar(20))+'"'
END
 
would do the trick, To be called like dbo.ftinstr( floatval ).
 
Maybe I can beautify it a little still ...