How to make textbox Invisible when viewed on screen but visible when printed?

I have a couple reports that have parameters on them. Problem is when the report is printed, the parameters are not displayed.

To solve this, I have added the selected values to the header section of the report in a text box. I now want to find away to hide these values when the report is being viewed on screen but visible when printed. Any suggestions are welcome. Thanks

Does anybody have any suggestions on this or a workaround. I want the user to be able to know the parameters they selected when they print the report.

Thanks

|||

Hello,

You could have another parameter called "Show Parameters" (defaulted to False), then set the visibility of your textbox based on this value. Of course, your users would have to check that box to show them before they printed/exported.

Hope this helps.

Jarret

|||Thanks, interesting and simple work around. I have implemented it. Let's see if the clients like it.

How to make subreport visible based on parameter condition?

Hi,

I have a subreport added to the main report and I want to make this report visible only when the parameter value is met.

Ex, I have a parameter CustName in the main report and want to show the subreport when the custName = xxxxx. There reports are parameter driven not data driven reports.

Any help is greatly appreciated.

Thanks,

Sirisha

When you are binding the Subreport and main report with a parameter , you can accomplish this by doing below steps.

1.) Click on Subreport and go the properties.

2.) In the second tab which is "Visibility" click on Expression radiobutton and press Fx button and paste this code.

=IIF(Fields!CustName.Value= "xxxxx",False,True)

Hope this helps...

|||Thanks Deepak, it worked great

How to make different instances of SQL Server visible to each other?

Two instances of SQL Server 2005 cannot "see" each other. One is Developer
edition and one is Standard edition. Standard editon is running under
Virtual PC. I would appreciate any suggestions on how make these two
instances visible to each other.
Thanks,
Keith
This should work pretty much like connecting any other two computers.
1) Can each computer ping the other successfully using TCP/IP? If not, it's
a virtual server problem.
2) Is the firewall on each computer configured to allow access through TCP
port 1433 (if you are using the default settings for a default instance)? If
not, change the firewall settings.
3) Is each SQL Server accepting TCP/IP connections? Check using the SQL
Server Surface Area Configuration tool.
4) If you are not using the default TCP port or if you installed a named
instance is the SQL Server Browser service running on each computer/virtual
machine to resolve the instance name to the port number? If not, start the
SQL Server Browser service.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"keith" <kbrickey@.dslextreme.com> wrote in message
news:%23QcBFI0SHHA.3428@.TK2MSFTNGP04.phx.gbl...
> Two instances of SQL Server 2005 cannot "see" each other. One is Developer
> edition and one is Standard edition. Standard editon is running under
> Virtual PC. I would appreciate any suggestions on how make these two
> instances visible to each other.
> Thanks,
> Keith
>

How to make different instances of SQL Server visible to each other?

Two instances of SQL Server 2005 cannot "see" each other. One is Developer
edition and one is Standard edition. Standard editon is running under
Virtual PC. I would appreciate any suggestions on how make these two
instances visible to each other.
Thanks,
KeithThis should work pretty much like connecting any other two computers.
1) Can each computer ping the other successfully using TCP/IP? If not, it's
a virtual server problem.
2) Is the firewall on each computer configured to allow access through TCP
port 1433 (if you are using the default settings for a default instance)? If
not, change the firewall settings.
3) Is each SQL Server accepting TCP/IP connections? Check using the SQL
Server Surface Area Configuration tool.
4) If you are not using the default TCP port or if you installed a named
instance is the SQL Server Browser service running on each computer/virtual
machine to resolve the instance name to the port number? If not, start the
SQL Server Browser service.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"keith" <kbrickey@.dslextreme.com> wrote in message
news:%23QcBFI0SHHA.3428@.TK2MSFTNGP04.phx.gbl...
> Two instances of SQL Server 2005 cannot "see" each other. One is Developer
> edition and one is Standard edition. Standard editon is running under
> Virtual PC. I would appreciate any suggestions on how make these two
> instances visible to each other.
> Thanks,
> Keith
>|||Hi,
in addition you will have to make sure that you configured your firewall to
let the Virtual PC access your host PC. it sometimes saw this, that although
ICMP was working the host refused to establish connections to the VPC if
they used Shared networking and not NAT.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:F0034F02-B236-4402-9180-7817FA21CB9F@.microsoft.com...
> This should work pretty much like connecting any other two computers.
> 1) Can each computer ping the other successfully using TCP/IP? If not,
> it's a virtual server problem.
> 2) Is the firewall on each computer configured to allow access through TCP
> port 1433 (if you are using the default settings for a default instance)?
> If not, change the firewall settings.
> 3) Is each SQL Server accepting TCP/IP connections? Check using the SQL
> Server Surface Area Configuration tool.
> 4) If you are not using the default TCP port or if you installed a named
> instance is the SQL Server Browser service running on each
> computer/virtual machine to resolve the instance name to the port number?
> If not, start the SQL Server Browser service.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "keith" <kbrickey@.dslextreme.com> wrote in message
> news:%23QcBFI0SHHA.3428@.TK2MSFTNGP04.phx.gbl...
>