I recently ran into a situation where a price data element was stored in a float field without the decimal. The field could contain values of variable decimal lengths, so the value "130445" could be "130.445" or "1.30445", depending on the value stored in another field that indicated the decimal length to the right of the decimal point.
This T-SQL code sample shows how to deal with this somewhat tricky conversion:
Declare @ImplDecimal int
Declare @TargetNumber float
Set @TargetNumber = 130445
Set @ImplDecimal = 3
Select @TargetNumber as TargetNumber, @ImplDecimal as ImpliedDecimal, @TargetNumber / POWER(10,@ImplDecimal) as Result
Set @TargetNumber = 130445
Set @ImplDecimal = 5
Select @TargetNumber as TargetNumber, @ImplDecimal as ImpliedDecimal, @TargetNumber / POWER(10,@ImplDecimal) as Result