Dear ALl,
How to change dpi/resolutoin of the tiff being exported.
Thank you
Regards,
AngusCheck
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_soapapi_dev_9xip.asp?frame=true.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"angus" <angus@.angus.com> wrote in message
news:OHDxNeSeEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Dear ALl,
> How to change dpi/resolutoin of the tiff being exported.
> Thank you
> Regards,
> Angus
>
Showing posts with label regards. Show all posts
Showing posts with label regards. Show all posts
Friday, March 23, 2012
Monday, March 12, 2012
How to call subreports from a main report
HI there,
I want to know if someone know how to call subreports that depends from one
main report.
Could you help me?
Regards,
Oscar.On Nov 9, 10:48 am, Remigio Oscar Iglesias - Argentina
<RemigioOscarIglesiasArgent...@.discussions.microsoft.com> wrote:
> I want to know if someone know how to call subreports that depends from one
> main report.
Create a Main Report (named "Report A").
Create a second report (the Subreport named "Report B") that receives
a Parameter. Use the Parameter in the Data query.
Add a Subreport object to the Main Report, and open the object's
Property window. Set the object's "Subreport" Property to the name of
the Sub Report (Report B). Go to the Parameters Tab. Set Report B's
Parameter to a value calculated in Report A. Now query that is made
in Report B depends on data provided in Report A.
-- Scott|||Note that your subreport is just a regular report you are embedding into
your main report. The subreport should be designed with parameters. Test the
subreport fully and then Drag and drop your subreport onto the main report.
Right mouse click on subreport, parameters. Map the parameter of the
subreport to whatever you want from the main report (it can be a field if
you are doing something like a master-detail report, you can base it on the
parameters for the main report).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Remigio Oscar Iglesias - Argentina"
<RemigioOscarIglesiasArgentina@.discussions.microsoft.com> wrote in message
news:BDD3CE41-8B8B-48BD-92A1-0C0BA75FE5EB@.microsoft.com...
> HI there,
> I want to know if someone know how to call subreports that depends from
> one
> main report.
> Could you help me?
> Regards,
> Oscar.
>
I want to know if someone know how to call subreports that depends from one
main report.
Could you help me?
Regards,
Oscar.On Nov 9, 10:48 am, Remigio Oscar Iglesias - Argentina
<RemigioOscarIglesiasArgent...@.discussions.microsoft.com> wrote:
> I want to know if someone know how to call subreports that depends from one
> main report.
Create a Main Report (named "Report A").
Create a second report (the Subreport named "Report B") that receives
a Parameter. Use the Parameter in the Data query.
Add a Subreport object to the Main Report, and open the object's
Property window. Set the object's "Subreport" Property to the name of
the Sub Report (Report B). Go to the Parameters Tab. Set Report B's
Parameter to a value calculated in Report A. Now query that is made
in Report B depends on data provided in Report A.
-- Scott|||Note that your subreport is just a regular report you are embedding into
your main report. The subreport should be designed with parameters. Test the
subreport fully and then Drag and drop your subreport onto the main report.
Right mouse click on subreport, parameters. Map the parameter of the
subreport to whatever you want from the main report (it can be a field if
you are doing something like a master-detail report, you can base it on the
parameters for the main report).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Remigio Oscar Iglesias - Argentina"
<RemigioOscarIglesiasArgentina@.discussions.microsoft.com> wrote in message
news:BDD3CE41-8B8B-48BD-92A1-0C0BA75FE5EB@.microsoft.com...
> HI there,
> I want to know if someone know how to call subreports that depends from
> one
> main report.
> Could you help me?
> Regards,
> Oscar.
>
Wednesday, March 7, 2012
How to call .NET components in SQL Server
Hi,
Can any guide me, how to register .NET component in SQL Server 2000 and call
the method.
Thanks & Regards
V.EdayachandranYou cannot call a .NET component from SQL Server 2000 directly. Either you
need to use an extended stored procedure wrapper to call it or try to create
a CCW for the component and then invoke the same using sp_OA* procedures.
Remember these are NOT supported by MS though they work ...
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"EDA" <EDA@.discussions.microsoft.com> wrote in message
news:DE695846-A575-4B0F-B4C9-E4FCBD5F559B@.microsoft.com...
> Hi,
> Can any guide me, how to register .NET component in SQL Server 2000 and
call
> the method.
> Thanks & Regards
> V.Edayachandran|||To add to Vinod's response, here's a link to an MSKB article on the subject:
http://support.microsoft.com/default.aspx?scid=kb;en-us;322884.
You'll have a lot more options in SQL 2005, though.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"EDA" <EDA@.discussions.microsoft.com> wrote in message
news:DE695846-A575-4B0F-B4C9-E4FCBD5F559B@.microsoft.com...
> Hi,
> Can any guide me, how to register .NET component in SQL Server 2000 and
> call
> the method.
> Thanks & Regards
> V.Edayachandran|||"Vinod Kumar" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
news:cuadre$1f6$1@.news01.intel.com...
> You cannot call a .NET component from SQL Server 2000 directly. Either you
> need to use an extended stored procedure wrapper to call it or try to
> create
> a CCW for the component and then invoke the same using sp_OA* procedures.
While it's not supported to call .NET components directly from SQL Server,
indirect methods which don't load the CLR into the SQL Server process are
OK. So you can use the MSXML2.ServerXMLHTTP COM library to invoke a .NET
web service, or you can install your COM-Callable .NET component in COM+ as
a COM+ server application. In the first case you are loading an unmanaged
COM library in the SQL Server process, and in the second, COM is supplying
an unmanaged proxy for the SQL Server process and remoting calls over to a
COM+ process where the CLR and and your component are loaded.
David
Can any guide me, how to register .NET component in SQL Server 2000 and call
the method.
Thanks & Regards
V.EdayachandranYou cannot call a .NET component from SQL Server 2000 directly. Either you
need to use an extended stored procedure wrapper to call it or try to create
a CCW for the component and then invoke the same using sp_OA* procedures.
Remember these are NOT supported by MS though they work ...
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"EDA" <EDA@.discussions.microsoft.com> wrote in message
news:DE695846-A575-4B0F-B4C9-E4FCBD5F559B@.microsoft.com...
> Hi,
> Can any guide me, how to register .NET component in SQL Server 2000 and
call
> the method.
> Thanks & Regards
> V.Edayachandran|||To add to Vinod's response, here's a link to an MSKB article on the subject:
http://support.microsoft.com/default.aspx?scid=kb;en-us;322884.
You'll have a lot more options in SQL 2005, though.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"EDA" <EDA@.discussions.microsoft.com> wrote in message
news:DE695846-A575-4B0F-B4C9-E4FCBD5F559B@.microsoft.com...
> Hi,
> Can any guide me, how to register .NET component in SQL Server 2000 and
> call
> the method.
> Thanks & Regards
> V.Edayachandran|||"Vinod Kumar" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
news:cuadre$1f6$1@.news01.intel.com...
> You cannot call a .NET component from SQL Server 2000 directly. Either you
> need to use an extended stored procedure wrapper to call it or try to
> create
> a CCW for the component and then invoke the same using sp_OA* procedures.
While it's not supported to call .NET components directly from SQL Server,
indirect methods which don't load the CLR into the SQL Server process are
OK. So you can use the MSXML2.ServerXMLHTTP COM library to invoke a .NET
web service, or you can install your COM-Callable .NET component in COM+ as
a COM+ server application. In the first case you are loading an unmanaged
COM library in the SQL Server process, and in the second, COM is supplying
an unmanaged proxy for the SQL Server process and remoting calls over to a
COM+ process where the CLR and and your component are loaded.
David
Subscribe to:
Posts (Atom)