No data to print

Hello Guys,
I am having hard time printing "No data to print" when there are no records returned by the report. Rightnow report prints without data but with all column headings. I would appreciate hearing from you soon.
Thanks
Dilemma

:wave:Hi,
In all headers suppress events write the formula as below
if isnull({DatabaseFeild}) =True then True
Place a new header in the header showing the value "No data to Print"
Now in the suppress event of this header write the formula as
if isnull({DatabaseFeild}) =false then True
Madhivanan|||Hello Madhi,

Thanks for the reply. I appreciate your help.

I am just wondering how do u write code header supress event. Do u have to write some code in your eg. VB or PB's event or in crystal report designer itself ? Unfortunately I am using PowreBuilder (pb) for the development.

Thanks
Dilemma|||Hi,
You can use this code in the crystal report itself.
Right click on header and select format section. A pop up menu will appear. There will be a check box labelled as Suppress. In parallel to that a button labelled X-2 is there. Click that button and write the coding I have mentioned. You have to this process for each header. To display "No data to Print", just add a text object and write it as "No data to Print" and in the suppress option write the second formula.

Madhivanan

no border

when i print my report i do not want to have border

how do i do?

Thanks

nobody |||

This is not a chat ;)

What about going to report properties (Report -> Report properties) and setting the left/right/bottom/top border to 0?

|||

i did try before i post my question here and for some reason its not allowing you to put 0 in the border

you get error when you try to put 0

|||

what borders do you mean?
the border around an element (e.g. a black line), or the white border of the report on the printed page(called margin I think)?

In the report-properties you can set the margin to 0, but you cant set a element-border to 0 to do so you have to set border-style to none..

Best regards
Benjamin

newline character in sqlserver

what is the newline character in sqlserver.
My problem is ,I have to display text (say "Hi \n abcd\n hhh\n") where \n is the newline.
But when i print this in sqlserver storedproc,Its displaying as it is instead of newlines.

please help

thxyou can do it via asp.net when you pass in the string do a string.replace of newlines ..something like

txtstmtbdy.text.replace(environment.newline,"<br>")

and when you display it the html is automatically parsed by the browser..so you dont have to worry about messing with it in sql server.

hth|||I assume you mean displaying the results in Query Analyser? If so I believe its the good old fashioned ASCII 10+13

Newbie: printing question

Please (do not) confirm:
- To have a "print" button on report in order to print a report and not the
html page do I need to wait for sp2?
When could the sp2 be available?Yes, print functionality will be available in SP2 in the form of a
downloadable control. SP 2 is currently undergoing beta testing and it
should be out before the end of the year based on what I know. So, make a
wish to Santa if you've been a good boy :-)
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Marko Linke" <mlinke@.inet.hr> wrote in message
news:ufPVShU0EHA.4004@.tk2msftngp13.phx.gbl...
> Please (do not) confirm:
> - To have a "print" button on report in order to print a report and not
the
> html page do I need to wait for sp2?
> When could the sp2 be available?
>|||Sure it helps, thank you very much! So, then, first I'll start by helping
people cross the street and polishing my shoes for Santa's name day 6th
December in hope SP2 will fit my chimney later on. I'll also tip my boss to
do the same :-)
Best regards,
Marko
"Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
news:%23rZG7cZ0EHA.3156@.TK2MSFTNGP10.phx.gbl...
> Yes, print functionality will be available in SP2 in the form of a
> downloadable control. SP 2 is currently undergoing beta testing and it
> should be out before the end of the year based on what I know. So, make a
> wish to Santa if you've been a good boy :-)
> --
> Hope this helps.
> ---
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ---
> "Marko Linke" <mlinke@.inet.hr> wrote in message
> news:ufPVShU0EHA.4004@.tk2msftngp13.phx.gbl...
>> Please (do not) confirm:
>> - To have a "print" button on report in order to print a report and not
> the
>> html page do I need to wait for sp2?
>> When could the sp2 be available?
>>
>|||You never know what works :-)
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Marko Linke" <mlinke@.inet.hr> wrote in message
news:uhiv34e0EHA.3588@.TK2MSFTNGP14.phx.gbl...
> Sure it helps, thank you very much! So, then, first I'll start by helping
> people cross the street and polishing my shoes for Santa's name day 6th
> December in hope SP2 will fit my chimney later on. I'll also tip my boss
to
> do the same :-)
> Best regards,
> Marko
> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
> news:%23rZG7cZ0EHA.3156@.TK2MSFTNGP10.phx.gbl...
> > Yes, print functionality will be available in SP2 in the form of a
> > downloadable control. SP 2 is currently undergoing beta testing and it
> > should be out before the end of the year based on what I know. So, make
a
> > wish to Santa if you've been a good boy :-)
> >
> > --
> > Hope this helps.
> >
> > ---
> > Teo Lachev, MVP [SQL Server], MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > Publisher website: http://www.manning.com/lachev
> > Buy it from Amazon.com: http://shrinkster.com/eq
> > Home page and blog: http://www.prologika.com/
> > ---
> >
> > "Marko Linke" <mlinke@.inet.hr> wrote in message
> > news:ufPVShU0EHA.4004@.tk2msftngp13.phx.gbl...
> >> Please (do not) confirm:
> >>
> >> - To have a "print" button on report in order to print a report and not
> > the
> >> html page do I need to wait for sp2?
> >>
> >> When could the sp2 be available?
> >>
> >>
> >
> >
>

newbie: logging for stored procs

ok when debugging a stored proc, yes i can see print output etc in sql
query analyzer. but when the proc is called in production, i dont see that
output; moreover, im new and wondering what are the typical ways that you
all log stuff from a stored proc, etc.
is something like this common?
http://www.databasejournal.com/feat...cle.php/1467591jimbo-black wrote:
> ok when debugging a stored proc, yes i can see print output etc in sql
> query analyzer. but when the proc is called in production, i dont
> see that output; moreover, im new and wondering what are the typical
> ways that you all log stuff from a stored proc, etc.
> is something like this common?
> http://www.databasejournal.com/feat...cle.php/1467591
Presumably, you have PRINT statements in procedures while they are in
development for debugging purposes and those PRINT statements are
removed for production. If what you need is a parameter-driven method to
execute a procedure with logging, then you can use conditional
statements in the procedure to log to a table as the article explains
(or even issue PRINT statements for interactive testing). In general,
though, it's better to do this type of work in development and keep your
procedure code to a minimum. For batch routines that might need to log
their lengthly processes and progress, a logging table would be the way
to go.
David Gugick
Quest Software
www.imceda.com
www.quest.com

newbie: logging for stored procs

ok when debugging a stored proc, yes i can see print output etc in sql
query analyzer. but when the proc is called in production, i dont see that
output; moreover, im new and wondering what are the typical ways that you
all log stuff from a stored proc, etc.
is something like this common?
http://www.databasejournal.com/features/mssql/article.php/1467591jimbo-black wrote:
> ok when debugging a stored proc, yes i can see print output etc in sql
> query analyzer. but when the proc is called in production, i dont
> see that output; moreover, im new and wondering what are the typical
> ways that you all log stuff from a stored proc, etc.
> is something like this common?
> http://www.databasejournal.com/features/mssql/article.php/1467591
Presumably, you have PRINT statements in procedures while they are in
development for debugging purposes and those PRINT statements are
removed for production. If what you need is a parameter-driven method to
execute a procedure with logging, then you can use conditional
statements in the procedure to log to a table as the article explains
(or even issue PRINT statements for interactive testing). In general,
though, it's better to do this type of work in development and keep your
procedure code to a minimum. For batch routines that might need to log
their lengthly processes and progress, a logging table would be the way
to go.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com

newbie: logging for stored procs

ok when debugging a stored proc, yes i can see print output etc in sql
query analyzer. but when the proc is called in production, i dont see that
output; moreover, im new and wondering what are the typical ways that you
all log stuff from a stored proc, etc.
is something like this common?
http://www.databasejournal.com/featu...le.php/1467591
jimbo-black wrote:
> ok when debugging a stored proc, yes i can see print output etc in sql
> query analyzer. but when the proc is called in production, i dont
> see that output; moreover, im new and wondering what are the typical
> ways that you all log stuff from a stored proc, etc.
> is something like this common?
> http://www.databasejournal.com/featu...le.php/1467591
Presumably, you have PRINT statements in procedures while they are in
development for debugging purposes and those PRINT statements are
removed for production. If what you need is a parameter-driven method to
execute a procedure with logging, then you can use conditional
statements in the procedure to log to a table as the article explains
(or even issue PRINT statements for interactive testing). In general,
though, it's better to do this type of work in development and keep your
procedure code to a minimum. For batch routines that might need to log
their lengthly processes and progress, a logging table would be the way
to go.
David Gugick
Quest Software
www.imceda.com
www.quest.com