Print format of Linked Reports

Having just discovered that linked reports do not retain any print formating applied to the original report I thought I'd check out the forum and see if it was just me having a senile moment or if Microsoft had in fact dropped a clanger of massive proportion.

After reading one or two questions from other RS users it does seem as if Microsoft have stuck again and completely diminished a useful feature by stripping it of anything, well....... useful. Well done MS, you once again have my applause for mind-boggling ineptitude of what should be impossible magnitude. Ah, you've got to laugh.

Maybe this and other bugs with RS2005 will be ironed out in Microsoft Reporting Services 2008 - The Search for More Money.

I was also disappointed that linked reports did not retain the print format from the source report. Below is a link with a couple of possible work arounds.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1880227&SiteID=1

|||

Thanks, I did come across these when I originally searched this problem on the forum but I haven't yet had chance to read or try any of them.

Using scripts and code kind of makes me feel like I've just bought a new Jag but I'm still required to delve into the engine bay and hot-wire it because the key fails to work, if you know what I mean. In any case there doesn't seem to be any alternative so I'll have to get my fingers dirty.

sql

Pricision of float

Hi,

Just wonder why

PRINT CAST(0.0573542567654 AS float)

will give the rounded reult

0.0573543

rather than the original number?

"float" should be 'big' enough to hold numbers that have even more
decimal places. How come it round up at the 7 decimal place?

since I need to do some calculations with accumulated values. The
rounded figure will cause significant error after a number of opertions.

Are there any way to work around it?

thanks

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Float is never exact. You will need decimal or numeric instead.

--
-oj
http://www.rac4sql.net

"Benny" <anonymous@.devdex.com> wrote in message
news:3ff9ec52$0$202$75868355@.news.frii.net...
> Hi,
> Just wonder why
> PRINT CAST(0.0573542567654 AS float)
> will give the rounded reult
> 0.0573543
> rather than the original number?
> "float" should be 'big' enough to hold numbers that have even more
> decimal places. How come it round up at the 7 decimal place?
> since I need to do some calculations with accumulated values. The
> rounded figure will cause significant error after a number of opertions.
> Are there any way to work around it?
> thanks
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Benny (anonymous@.devdex.com) writes:
> Just wonder why
> PRINT CAST(0.0573542567654 AS float)
> will give the rounded reult
> 0.0573543
> rather than the original number?
> "float" should be 'big' enough to hold numbers that have even more
> decimal places. How come it round up at the 7 decimal place?
> since I need to do some calculations with accumulated values. The
> rounded figure will cause significant error after a number of opertions.
> Are there any way to work around it?

PRINT does not work on floats, it works with string data, so there is
an implicit conversion to varchar, and that conversion gives you
seven decimals by default.

Here is one option:

PRINT convert(varchar(30), CAST(0.0573542567654 AS float), 2)

You can also use the str() function to format floats as string. Look
up this function in Books Online.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp