| Groups | Blog | Home |
sql server reporting services : global code
line for custom code and it will tell you all about it. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Servé La" <blabla@bestaatniet.nl> wrote in message news:uTpyCPrCFHA.3924@TK2MSFTNGP15.phx.gbl... > Is there a place where I can put custom code so that all reports in a > solution can access the same code? > I now copy the code into every new report I create > >
I haven't done this but I think it would work. It looks to me that
report.rdl in this directory: C:\Program Files\Microsoft SQL Server\80\Tools\Report Designer\ProjectItems\ReportProject Is what is used by the report wizard. My guess is if you change this then all the new reports would have the code. Save a copy of it just in case. Let me know if that works for you. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Servé La" <blabla@bestaatniet.nl> wrote in message news:uS0vSqsCFHA.3324@TK2MSFTNGP15.phx.gbl... > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> schreef in bericht > news:%2393IKdsCFHA.3376@TK2MSFTNGP12.phx.gbl... > > You can have assemblies that are shared between reports. Search books on > > line for custom code and it will tell you all about it. > > Thats not what I meant. The code for calling the assemblies will have to be > duplicated in every report one creates. > >
You are not being consistent here. On the one hand you said you understood
about using custom assemblies. On the other hand you posted this. Your code can go in a custom assembly once. Then all you have to do is reference that assembly in your reports. You do not have to have that function defined in each and every report. As I suggested before, read up on custom code. You can do custom code two ways, code behind report and in your own assembly. What you are talking about here is code behind report. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Servé La" <blabla@bestaatniet.nl> wrote in message news:%23whb6AtCFHA.1188@tk2msftngp13.phx.gbl... > > "Frank Matthiesen" <fm@xax.de> schreef in bericht > news:36hi9eF50g2hqU1@individual.net... > > Servé La wrote: > > > Thats not what I meant. The code for calling the assemblies will have > > > to be duplicated in every report one creates. > > > > I did'nt understand your question. Each report is like a single programm. > > If i need an assembly in two programms, i have to write > > IMPORTS myassemblyclass > > in BOTH programms > > Suppose you have created a component where you have to set a few properties > and then calculate some value. > You create a function for this like the following: > > Function Compute(name as String, x as Integer, y as Integer, z as Integer) > as Integer > Dim obj as new MyComponents.Component(name) > > obj.X = x > obj.Y = y > obj.Z = z > > Try > Compute = obj.Compute() > Catch e as OopsException > Compute = -1 > End Try > > End Function > > You then want to use this function in a few reports. Right now I see no > other way then to put that code in every report and call it, while I > expected to put that function somewhere globally where all reports could > access it. In reality the code gets a lot more complex very fast. > >
Is there a place where I can put custom code so that all reports in a
solution can access the same code? I now copy the code into every new report I create
Could you not store the function as a 'stored procedure' in the database
then just call the stored procedure as you need it? Dale [quoted text, click to view] "Servé La" <blabla@bestaatniet.nl> wrote in message news:%23whb6AtCFHA.1188@tk2msftngp13.phx.gbl... > > "Frank Matthiesen" <fm@xax.de> schreef in bericht > news:36hi9eF50g2hqU1@individual.net... > > Servé La wrote: > > > Thats not what I meant. The code for calling the assemblies will have > > > to be duplicated in every report one creates. > > > > I did'nt understand your question. Each report is like a single programm. > > If i need an assembly in two programms, i have to write > > IMPORTS myassemblyclass > > in BOTH programms > > Suppose you have created a component where you have to set a few properties > and then calculate some value. > You create a function for this like the following: > > Function Compute(name as String, x as Integer, y as Integer, z as Integer) > as Integer > Dim obj as new MyComponents.Component(name) > > obj.X = x > obj.Y = y > obj.Z = z > > Try > Compute = obj.Compute() > Catch e as OopsException > Compute = -1 > End Try > > End Function > > You then want to use this function in a few reports. Right now I see no > other way then to put that code in every report and call it, while I > expected to put that function somewhere globally where all reports could > access it. In reality the code gets a lot more complex very fast. > >
"Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> schreef in bericht news:%2393IKdsCFHA.3376@TK2MSFTNGP12.phx.gbl... [quoted text, click to view] > You can have assemblies that are shared between reports. Search books on > line for custom code and it will tell you all about it. Thats not what I meant. The code for calling the assemblies will have to be duplicated in every report one creates.
[quoted text, click to view]
Servé La wrote: > Thats not what I meant. The code for calling the assemblies will have > to be duplicated in every report one creates. I did'nt understand your question. Each report is like a single programm. If i need an assembly in two programms, i have to write IMPORTS myassemblyclass in BOTH programms frank
"Frank Matthiesen" <fm@xax.de> schreef in bericht news:36hi9eF50g2hqU1@individual.net... [quoted text, click to view] > Servé La wrote: > > Thats not what I meant. The code for calling the assemblies will have > > to be duplicated in every report one creates. > > I did'nt understand your question. Each report is like a single programm. > If i need an assembly in two programms, i have to write > IMPORTS myassemblyclass > in BOTH programms Suppose you have created a component where you have to set a few properties and then calculate some value. You create a function for this like the following: Function Compute(name as String, x as Integer, y as Integer, z as Integer) as Integer Dim obj as new MyComponents.Component(name) obj.X = x obj.Y = y obj.Z = z Try Compute = obj.Compute() Catch e as OopsException Compute = -1 End Try End Function You then want to use this function in a few reports. Right now I see no other way then to put that code in every report and call it, while I expected to put that function somewhere globally where all reports could access it. In reality the code gets a lot more complex very fast.
You are still missing the point. You can have code behind and you can have
custom assemblies. You can definitely put your common functions in a custom assembly that all your reports will use. You can have both code behind and custom assemblies. The tricky part of custom assemblies is deployment of the assembly. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Servé La" <blabla@bestaatniet.nl> wrote in message news:%233S6lYODFHA.3256@tk2msftngp13.phx.gbl... > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> schreef in bericht > news:uvhbbYtCFHA.2540@TK2MSFTNGP09.phx.gbl... > > You are not being consistent here. On the one hand you said you understood > > about using custom assemblies. On the other hand you posted this. Your > code > > can go in a custom assembly once. Then all you have to do is reference > that > > assembly in your reports. You do not have to have that function defined in > > each and every report. > > > > As I suggested before, read up on custom code. You can do custom code two > > ways, code behind report and in your own assembly. What you are talking > > about here is code behind report. > > I guess I meant code behind then. I have some cases where methods need to be > called from code behind in a certain order so it would be nice to have this > functionality in one single function defined somewhere globally. > I take it the answer is "no you cant do this" then :) > >
"Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> schreef in bericht news:uvhbbYtCFHA.2540@TK2MSFTNGP09.phx.gbl... [quoted text, click to view] > You are not being consistent here. On the one hand you said you understood > about using custom assemblies. On the other hand you posted this. Your code > can go in a custom assembly once. Then all you have to do is reference that > assembly in your reports. You do not have to have that function defined in > each and every report. > > As I suggested before, read up on custom code. You can do custom code two > ways, code behind report and in your own assembly. What you are talking > about here is code behind report. I guess I meant code behind then. I have some cases where methods need to be called from code behind in a certain order so it would be nice to have this functionality in one single function defined somewhere globally. I take it the answer is "no you cant do this" then :)
"BruceLC" <brucelc@newsgroup.nospam> schreef in bericht news:OOGvMxRDFHA.1040@TK2MSFTNGP09.phx.gbl... [quoted text, click to view] > You are still missing the point. You can have code behind and you can have > custom assemblies. You can definitely put your common functions in a custom > assembly that all your reports will use. You can have both code behind and > custom assemblies. The tricky part of custom assemblies is deployment of the > assembly. I am talking about calling a custom assembly from code behind! It's about both!! The methods in the custom assembly need to be called within a certain order so this has to be done in code behind.
Try putting your common code in a custom assembly and then placing it into
GAC -- Alex Mineev Software Design Engineer. Report expressions; Code Access Security; Xml; SQE. This posting is provided "AS IS" with no warranties, and confers no rights [quoted text, click to view] "Servé La" <blabla@bestaatniet.nl> wrote in message news:uTpyCPrCFHA.3924@TK2MSFTNGP15.phx.gbl... > Is there a place where I can put custom code so that all reports in a > solution can access the same code? > I now copy the code into every new report I create > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |