Linking Reports in different projects

Is there a way to link reports from one project to reports in a second
project?You do this from report manager. Open up the properties of the report you
want to create a linked report of and then specify the location the linked
report should go in.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sfibich" <sfibich@.pfgc.com> wrote in message
news:eQM9U%2334EHA.1692@.TK2MSFTNGP10.phx.gbl...
> Is there a way to link reports from one project to reports in a second
> project?|||Bruce L-C [MVP] wrote:
> You do this from report manager. Open up the properties of the report you
> want to create a linked report of and then specify the location the linked
> report should go in.
>
But this does not work when reports are in different projects or is
there something I am missing?|||The way it works for me is each project is a directory on the web server. If
I have a project/directory that I want the same report to show in both then
from report manager (not from the IDE, you can not do this from within VS)
follow the directions I gave you below. Try one, it will make sense once you
do one.
"sfibich" <sfibich@.pfgc.com> wrote in message
news:ugXBpP44EHA.1564@.TK2MSFTNGP09.phx.gbl...
> Bruce L-C [MVP] wrote:
> > You do this from report manager. Open up the properties of the report
you
> > want to create a linked report of and then specify the location the
linked
> > report should go in.
> >
> But this does not work when reports are in different projects or is
> there something I am missing?|||Bruce L-C [MVP] wrote:
> The way it works for me is each project is a directory on the web server. If
> I have a project/directory that I want the same report to show in both then
> from report manager (not from the IDE, you can not do this from within VS)
> follow the directions I gave you below. Try one, it will make sense once you
> do one.
>
> "sfibich" <sfibich@.pfgc.com> wrote in message
> news:ugXBpP44EHA.1564@.TK2MSFTNGP09.phx.gbl...
>>Bruce L-C [MVP] wrote:
>>
>>You do this from report manager. Open up the properties of the report
> you
>>want to create a linked report of and then specify the location the
> linked
>>report should go in.
>>
>>But this does not work when reports are in different projects or is
>>there something I am missing?
>
>
Oh, now I see. Sorry I was so thick headed about this. This is going
to be a nightmare for me as I have many reports that need to be in sub
projects because of security reasons but most reports in one level need
to link down to the next level.
Thanks agian for you help.|||If I'm just creating a link from a textbox, I simply use the URL option of
the action property of the textbox to link to the report. You may still have
some security issues, but it works well for me.
"sfibich" wrote:
> Is there a way to link reports from one project to reports in a second
> project?
>

Linking reports

Does anyone know if it is possible to link two reports together?
For example, if you have a report showing customers with the number of
orders they have placed, can you then link to another report showing
details of the actual orders.
Hope this makes sense.
ChrisYes possible using drill through reports.
Amarnath
"chris.j.stubbs@.gmail.com" wrote:
> Does anyone know if it is possible to link two reports together?
> For example, if you have a report showing customers with the number of
> orders they have placed, can you then link to another report showing
> details of the actual orders.
> Hope this makes sense.
> Chris
>

Linking reports

Hello,
I am currently working on a project that involves tracking progress over several months. So, for the month of July, I need to show the results of June, May, etc. The easiest way I can think of doing this is to "connect" to the previous month's report. Can this be done? The only other options I can think of are:
A. have my July month recalculate all the values to the beginning of the year.
B. create an new table in my DB that will store the carry-over variables from the months before.
Any input would be appreciated.
No, you should make a query which give you all the summarized data. Then organize them into the report. And put a link in each month column to jump to the detailed report of the selected month.

The best solution is to design cubes and obtain data from it.

linking or installing reports into 05 repoting servier

I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link reports
in SQL 05 reporting services. The process in not the same as in SQL 2000.
Mike2005 works like 2000.
can you explain what do you try to do? or what you found different.
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:02A5E05A-6B57-4CDA-9DBD-8814388601F1@.microsoft.com...
> I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link
> reports
> in SQL 05 reporting services. The process in not the same as in SQL 2000.
> Mike|||Hi Jeie, well for starters in 2000 I went to the web interface and installed
the reporting scripts. When I instaklled the reporting services for 2000 it
created a web link on the desktop I would click on the link to connect,
pretty staright forward from there.
I guess basically I've not found the interface to install the scripts.
"Jeje" wrote:
> 2005 works like 2000.
> can you explain what do you try to do? or what you found different.
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:02A5E05A-6B57-4CDA-9DBD-8814388601F1@.microsoft.com...
> > I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link
> > reports
> > in SQL 05 reporting services. The process in not the same as in SQL 2000.
> >
> > Mike
>|||well, there is no link created anywhere.
you have to add it in your favorites by yourself.
by default the URL is:
http://server/reports
does it what you need?
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:147C2D38-E8EC-4697-B053-217B7FA97DBD@.microsoft.com...
> Hi Jeie, well for starters in 2000 I went to the web interface and
> installed
> the reporting scripts. When I instaklled the reporting services for 2000
> it
> created a web link on the desktop I would click on the link to connect,
> pretty staright forward from there.
> I guess basically I've not found the interface to install the scripts.
> "Jeje" wrote:
>> 2005 works like 2000.
>> can you explain what do you try to do? or what you found different.
>> "Mike" <Mike@.discussions.microsoft.com> wrote in message
>> news:02A5E05A-6B57-4CDA-9DBD-8814388601F1@.microsoft.com...
>> > I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link
>> > reports
>> > in SQL 05 reporting services. The process in not the same as in SQL
>> > 2000.
>> >
>> > Mike
>>

Linking back to ProClarity Analytics reports from SQL Server 2005 Reporting Services failed

Hi, all here,

Thank you very much for your kind attention.

I encountered a problem when linking back to ProClarity Analytics views from SQL Server 2005 Reporting Services Server (the reports on SQL Server 2005 Reporting Services Server is export from ProClarity). The error message is as below:

Server object error 'ASP 0177 : 800401f3'

Server.CreateObject Failed

/pas/en/src/PRSQuery.asp, line 50

800401f3

Note: this error only occured when linking back using option:'data on this report', no error occured when using option'analyze in a ProClarity server page'.

Would please any expert here give me any guidance and advices for that.

Thanks a lot in advance for that.

With best regards,

Yours sincerely,

Hi

I encountered the same problem. My solution is posted on my blog:
http://www.cubido.at/Blog/tabid/176/EntryID/177/Default.aspx

Linking Access to SQL Server

Hi,

I have an existing Access DB with many Tables, Forms, Queries and Reports. I need to put a SQL Server Back end on this database.

Do I need to code a mirror images of these objects or is there some way to export these into SQL Server?

Also, where do I deal with assigning usernames and passwords? Access or SQL Server. I need to have different views for different users based upon their rights (user, admin)

Thanks,

Mark

There is a full upsizing process that will handle all this for you. Read more here:

http://www.microsoft.com/sql/solutions/migration/access/default.mspx

|||

Hi Mark:

I am not sure if I understand your questions entirely.

If you are looking a way to convert your access database to sql database, following is the link to MSDN article that may help:

http://msdn2.microsoft.com/en-us/library/aa164792(office.10).aspx

About second part of your questions (usernames and password). Could you please provide more information?

Thanks.

server using the OLEDB for ODBC Driver

I have an ODBC driver to a non-SQL database that contains legacy data that I
need to reference in my application/reports. I had originally hoped to use a
linked server using the OLEDB for ODBC provider to access the data and so be
able to create applications/reports using data stored in SQL Server 2000 and
the legacy database via a single connection.
The problem is that, according to the ODBC drive vendor, when I use the 4
part name to refer to my linked server, SQL Server only passes the driver
the base select statement without any where clause resulting in the entire
table being returned to SQL Server which then applies the filter. This gives
me an average time of 8 minutes to return a single record of a 46,000 row
table.
If I use the OPENQUERY function the same select statement takes about 2
seconds. Unfortunately though, OPENQUERY does not accept a variables as a
parameter and so the select statement must be a hard coded string which
makes it unsuitable for any but a static view.
Any suggestions on a workaround for this?You can build the entire SQL string, e.g. select * from
openquery(server, 'etc...') , and pass the string into an
EXEC(). You can find examples in this article:
HOW TO: Pass a Variable to a Linked Server Query
http://support.microsoft.com/?id=314520
-Sue
On Wed, 11 Aug 2004 12:37:48 -0500, "Charles J Ryan"
<charlesryan1@.msn.com> wrote:

>I have an ODBC driver to a non-SQL database that contains legacy data that
I
>need to reference in my application/reports. I had originally hoped to use
a
>linked server using the OLEDB for ODBC provider to access the data and so b
e
>able to create applications/reports using data stored in SQL Server 2000 an
d
>the legacy database via a single connection.
>The problem is that, according to the ODBC drive vendor, when I use the 4
>part name to refer to my linked server, SQL Server only passes the driver
>the base select statement without any where clause resulting in the entire
>table being returned to SQL Server which then applies the filter. This give
s
>me an average time of 8 minutes to return a single record of a 46,000 row
>table.
>If I use the OPENQUERY function the same select statement takes about 2
>seconds. Unfortunately though, OPENQUERY does not accept a variables as a
>parameter and so the select statement must be a hard coded string which
>makes it unsuitable for any but a static view.
>Any suggestions on a workaround for this?
>

server using the OLEDB for ODBC Driver

I have an ODBC driver to a non-SQL database that contains legacy data that I
need to reference in my application/reports. I had originally hoped to use a
linked server using the OLEDB for ODBC provider to access the data and so be
able to create applications/reports using data stored in SQL Server 2000 and
the legacy database via a single connection.
The problem is that, according to the ODBC drive vendor, when I use the 4
part name to refer to my linked server, SQL Server only passes the driver
the base select statement without any where clause resulting in the entire
table being returned to SQL Server which then applies the filter. This gives
me an average time of 8 minutes to return a single record of a 46,000 row
table.
If I use the OPENQUERY function the same select statement takes about 2
seconds. Unfortunately though, OPENQUERY does not accept a variables as a
parameter and so the select statement must be a hard coded string which
makes it unsuitable for any but a static view.
Any suggestions on a workaround for this?
You can build the entire SQL string, e.g. select * from
openquery(server, 'etc...') , and pass the string into an
EXEC(). You can find examples in this article:
HOW TO: Pass a Variable to a Linked Server Query
http://support.microsoft.com/?id=314520
-Sue
On Wed, 11 Aug 2004 12:37:48 -0500, "Charles J Ryan"
<charlesryan1@.msn.com> wrote:

>I have an ODBC driver to a non-SQL database that contains legacy data that I
>need to reference in my application/reports. I had originally hoped to use a
>linked server using the OLEDB for ODBC provider to access the data and so be
>able to create applications/reports using data stored in SQL Server 2000 and
>the legacy database via a single connection.
>The problem is that, according to the ODBC drive vendor, when I use the 4
>part name to refer to my linked server, SQL Server only passes the driver
>the base select statement without any where clause resulting in the entire
>table being returned to SQL Server which then applies the filter. This gives
>me an average time of 8 minutes to return a single record of a 46,000 row
>table.
>If I use the OPENQUERY function the same select statement takes about 2
>seconds. Unfortunately though, OPENQUERY does not accept a variables as a
>parameter and so the select statement must be a hard coded string which
>makes it unsuitable for any but a static view.
>Any suggestions on a workaround for this?
>