Linking Multiple Data Sources

I have seen post regarding this topic before, but none have given a clear or
satisfactory answer.
I understand that multiple data sources cannot be directly linked. This
alone seems to be a major limitation to this product!
The standard answer seems to be to use subreports. This does not work in my
case as my report does not utilize any parameters. I want to see all records
from the one data set with userID linked to userID in the second data set
which comes from a totally different data source. The first data source is
Oracle the second is Fox Pro. Can anyone offer suggestions other than to buy
Crystal/Business Objects?
Thanks in advance.Subreports will work (or it sure seems that way to me).
Create the subreport (which is really just a report with a parameter). The
report that will be the subreport would have a parameter called UserID.
Create and test the report separately. Then drag and drop onto the first
report. Do a right mouse click on the subreport, parameters and then set the
report parameter for the subreport to the field userID.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"disappointed" <disappointed@.discussions.microsoft.com> wrote in message
news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
>I have seen post regarding this topic before, but none have given a clear
>or
> satisfactory answer.
> I understand that multiple data sources cannot be directly linked. This
> alone seems to be a major limitation to this product!
> The standard answer seems to be to use subreports. This does not work in
> my
> case as my report does not utilize any parameters. I want to see all
> records
> from the one data set with userID linked to userID in the second data set
> which comes from a totally different data source. The first data source
> is
> Oracle the second is Fox Pro. Can anyone offer suggestions other than to
> buy
> Crystal/Business Objects?
> Thanks in advance.|||Thanks for your prompt reply Bruce.
How do I create a parameter that does not prompt me to input a value? I
don't want a report for a specific userID, I want my report to contain all
userIDs. Are you talking about a report parameter or a dataset parameter?
Thanks.
"Bruce L-C [MVP]" wrote:
> Subreports will work (or it sure seems that way to me).
> Create the subreport (which is really just a report with a parameter). The
> report that will be the subreport would have a parameter called UserID.
> Create and test the report separately. Then drag and drop onto the first
> report. Do a right mouse click on the subreport, parameters and then set the
> report parameter for the subreport to the field userID.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
> >I have seen post regarding this topic before, but none have given a clear
> >or
> > satisfactory answer.
> >
> > I understand that multiple data sources cannot be directly linked. This
> > alone seems to be a major limitation to this product!
> >
> > The standard answer seems to be to use subreports. This does not work in
> > my
> > case as my report does not utilize any parameters. I want to see all
> > records
> > from the one data set with userID linked to userID in the second data set
> > which comes from a totally different data source. The first data source
> > is
> > Oracle the second is Fox Pro. Can anyone offer suggestions other than to
> > buy
> > Crystal/Business Objects?
> >
> > Thanks in advance.
>
>|||You are missing a key point. Except for testing you don't ever use the
subreport by itself. It is always called as a subreport. Note that you can
hide the subreport in list view so the user never sees it (this is done in
the property tab in report manager for the report)
The report you will use as a subreport will have a report parameter that is
tied to a query parameter for the report.
I assume you have a 1-M (although this works for 1-1 as well) relationship
going on here.
I think what you should do is back up and do a test. Create a very simple
report and subreport doing as I mention and just try it. Subreports are a
very important part of RS and to use RS to its fullest you need to
understand how to use them.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"disappointed" <disappointed@.discussions.microsoft.com> wrote in message
news:7EA2011F-530F-4343-99D3-67B0C990D45C@.microsoft.com...
> Thanks for your prompt reply Bruce.
> How do I create a parameter that does not prompt me to input a value? I
> don't want a report for a specific userID, I want my report to contain all
> userIDs. Are you talking about a report parameter or a dataset parameter?
> Thanks.
> "Bruce L-C [MVP]" wrote:
>> Subreports will work (or it sure seems that way to me).
>> Create the subreport (which is really just a report with a parameter).
>> The
>> report that will be the subreport would have a parameter called UserID.
>> Create and test the report separately. Then drag and drop onto the first
>> report. Do a right mouse click on the subreport, parameters and then set
>> the
>> report parameter for the subreport to the field userID.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
>> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
>> >I have seen post regarding this topic before, but none have given a
>> >clear
>> >or
>> > satisfactory answer.
>> >
>> > I understand that multiple data sources cannot be directly linked.
>> > This
>> > alone seems to be a major limitation to this product!
>> >
>> > The standard answer seems to be to use subreports. This does not work
>> > in
>> > my
>> > case as my report does not utilize any parameters. I want to see all
>> > records
>> > from the one data set with userID linked to userID in the second data
>> > set
>> > which comes from a totally different data source. The first data
>> > source
>> > is
>> > Oracle the second is Fox Pro. Can anyone offer suggestions other than
>> > to
>> > buy
>> > Crystal/Business Objects?
>> >
>> > Thanks in advance.
>>|||Thanks Bruce. Everything works great. My apologies for the evident
frustration in my first post.
"Bruce L-C [MVP]" wrote:
> You are missing a key point. Except for testing you don't ever use the
> subreport by itself. It is always called as a subreport. Note that you can
> hide the subreport in list view so the user never sees it (this is done in
> the property tab in report manager for the report)
> The report you will use as a subreport will have a report parameter that is
> tied to a query parameter for the report.
> I assume you have a 1-M (although this works for 1-1 as well) relationship
> going on here.
> I think what you should do is back up and do a test. Create a very simple
> report and subreport doing as I mention and just try it. Subreports are a
> very important part of RS and to use RS to its fullest you need to
> understand how to use them.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
> news:7EA2011F-530F-4343-99D3-67B0C990D45C@.microsoft.com...
> > Thanks for your prompt reply Bruce.
> >
> > How do I create a parameter that does not prompt me to input a value? I
> > don't want a report for a specific userID, I want my report to contain all
> > userIDs. Are you talking about a report parameter or a dataset parameter?
> >
> > Thanks.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Subreports will work (or it sure seems that way to me).
> >>
> >> Create the subreport (which is really just a report with a parameter).
> >> The
> >> report that will be the subreport would have a parameter called UserID.
> >> Create and test the report separately. Then drag and drop onto the first
> >> report. Do a right mouse click on the subreport, parameters and then set
> >> the
> >> report parameter for the subreport to the field userID.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
> >> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
> >> >I have seen post regarding this topic before, but none have given a
> >> >clear
> >> >or
> >> > satisfactory answer.
> >> >
> >> > I understand that multiple data sources cannot be directly linked.
> >> > This
> >> > alone seems to be a major limitation to this product!
> >> >
> >> > The standard answer seems to be to use subreports. This does not work
> >> > in
> >> > my
> >> > case as my report does not utilize any parameters. I want to see all
> >> > records
> >> > from the one data set with userID linked to userID in the second data
> >> > set
> >> > which comes from a totally different data source. The first data
> >> > source
> >> > is
> >> > Oracle the second is Fox Pro. Can anyone offer suggestions other than
> >> > to
> >> > buy
> >> > Crystal/Business Objects?
> >> >
> >> > Thanks in advance.
> >>
> >>
> >>
>
>|||No problem. For a certain set of problems Subreports are really the best and
sometimes only way to solve the problem. Note that you can even put a
subreport into an empty field of a table on the report.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"disappointed" <disappointed@.discussions.microsoft.com> wrote in message
news:2776A628-1C97-4E02-9E3E-D7683DB46652@.microsoft.com...
> Thanks Bruce. Everything works great. My apologies for the evident
> frustration in my first post.
> "Bruce L-C [MVP]" wrote:
>> You are missing a key point. Except for testing you don't ever use the
>> subreport by itself. It is always called as a subreport. Note that you
>> can
>> hide the subreport in list view so the user never sees it (this is done
>> in
>> the property tab in report manager for the report)
>> The report you will use as a subreport will have a report parameter that
>> is
>> tied to a query parameter for the report.
>> I assume you have a 1-M (although this works for 1-1 as well)
>> relationship
>> going on here.
>> I think what you should do is back up and do a test. Create a very simple
>> report and subreport doing as I mention and just try it. Subreports are a
>> very important part of RS and to use RS to its fullest you need to
>> understand how to use them.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
>> news:7EA2011F-530F-4343-99D3-67B0C990D45C@.microsoft.com...
>> > Thanks for your prompt reply Bruce.
>> >
>> > How do I create a parameter that does not prompt me to input a value?
>> > I
>> > don't want a report for a specific userID, I want my report to contain
>> > all
>> > userIDs. Are you talking about a report parameter or a dataset
>> > parameter?
>> >
>> > Thanks.
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Subreports will work (or it sure seems that way to me).
>> >>
>> >> Create the subreport (which is really just a report with a parameter).
>> >> The
>> >> report that will be the subreport would have a parameter called
>> >> UserID.
>> >> Create and test the report separately. Then drag and drop onto the
>> >> first
>> >> report. Do a right mouse click on the subreport, parameters and then
>> >> set
>> >> the
>> >> report parameter for the subreport to the field userID.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >>
>> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
>> >> >I have seen post regarding this topic before, but none have given a
>> >> >clear
>> >> >or
>> >> > satisfactory answer.
>> >> >
>> >> > I understand that multiple data sources cannot be directly linked.
>> >> > This
>> >> > alone seems to be a major limitation to this product!
>> >> >
>> >> > The standard answer seems to be to use subreports. This does not
>> >> > work
>> >> > in
>> >> > my
>> >> > case as my report does not utilize any parameters. I want to see
>> >> > all
>> >> > records
>> >> > from the one data set with userID linked to userID in the second
>> >> > data
>> >> > set
>> >> > which comes from a totally different data source. The first data
>> >> > source
>> >> > is
>> >> > Oracle the second is Fox Pro. Can anyone offer suggestions other
>> >> > than
>> >> > to
>> >> > buy
>> >> > Crystal/Business Objects?
>> >> >
>> >> > Thanks in advance.
>> >>
>> >>
>> >>
>>|||Hi everyone,
I was reading this post and it is along the lines of what I am looking to do
and wanted to verify sub reports will work. We do not have SSRS yet but have
it as a strong contender for our next reporting solution. We hope to make
the decision in the next few weeks and this is one area that we are held up
on. I know Crystal will do this for us, but we are hoping SSRS will do it.
We use SQL exclusively as our back end, and we are upgrading to 2005. We
have our data for reports coming from multiple databases within SQL. As a
result, we need to be able to gather information from database A, database B,
etc and incorporate the elements using some report parameters and database
parameters all one one report.
As a simple example we may have Customer names in Database A, and the
addresses to those customers in Database B, and the phone numbers to the
customers in Database C. When the report runs it will need to place all of
them on together in a tabular format so the customer name, address, and phone
number all line up accordingly. In addition, the user will be able to search
by any of these elements to get back one result set of all information.
Is all of this possible with SSRS 2005? If so is sub reports the best way
to accomplish this? We will be providing a solution for our applications
that provides an ADO.NET dataset so our applications can see the different
databases. Based on the tight integration to SQL Server, I don't image SSRS
could connect to this dataset as well.
Thanks for your assistance.
Brian G
"Bruce L-C [MVP]" wrote:
> No problem. For a certain set of problems Sub reports are really the best and
> sometimes only way to solve the problem. Note that you can even put a
> sub report into an empty field of a table on the report.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
> news:2776A628-1C97-4E02-9E3E-D7683DB46652@.microsoft.com...
> > Thanks Bruce. Everything works great. My apologies for the evident
> > frustration in my first post.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> You are missing a key point. Except for testing you don't ever use the
> >> subreport by itself. It is always called as a subreport. Note that you
> >> can
> >> hide the subreport in list view so the user never sees it (this is done
> >> in
> >> the property tab in report manager for the report)
> >>
> >> The report you will use as a subreport will have a report parameter that
> >> is
> >> tied to a query parameter for the report.
> >>
> >> I assume you have a 1-M (although this works for 1-1 as well)
> >> relationship
> >> going on here.
> >>
> >> I think what you should do is back up and do a test. Create a very simple
> >> report and subreport doing as I mention and just try it. Subreports are a
> >> very important part of RS and to use RS to its fullest you need to
> >> understand how to use them.
> >>
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
> >> news:7EA2011F-530F-4343-99D3-67B0C990D45C@.microsoft.com...
> >> > Thanks for your prompt reply Bruce.
> >> >
> >> > How do I create a parameter that does not prompt me to input a value?
> >> > I
> >> > don't want a report for a specific userID, I want my report to contain
> >> > all
> >> > userIDs. Are you talking about a report parameter or a dataset
> >> > parameter?
> >> >
> >> > Thanks.
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Subreports will work (or it sure seems that way to me).
> >> >>
> >> >> Create the subreport (which is really just a report with a parameter).
> >> >> The
> >> >> report that will be the subreport would have a parameter called
> >> >> UserID.
> >> >> Create and test the report separately. Then drag and drop onto the
> >> >> first
> >> >> report. Do a right mouse click on the subreport, parameters and then
> >> >> set
> >> >> the
> >> >> report parameter for the subreport to the field userID.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >>
> >> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
> >> >> >I have seen post regarding this topic before, but none have given a
> >> >> >clear
> >> >> >or
> >> >> > satisfactory answer.
> >> >> >
> >> >> > I understand that multiple data sources cannot be directly linked.
> >> >> > This
> >> >> > alone seems to be a major limitation to this product!
> >> >> >
> >> >> > The standard answer seems to be to use subreports. This does not
> >> >> > work
> >> >> > in
> >> >> > my
> >> >> > case as my report does not utilize any parameters. I want to see
> >> >> > all
> >> >> > records
> >> >> > from the one data set with userID linked to userID in the second
> >> >> > data
> >> >> > set
> >> >> > which comes from a totally different data source. The first data
> >> >> > source
> >> >> > is
> >> >> > Oracle the second is Fox Pro. Can anyone offer suggestions other
> >> >> > than
> >> >> > to
> >> >> > buy
> >> >> > Crystal/Business Objects?
> >> >> >
> >> >> > Thanks in advance.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Subreports are an easy way to do it. You can consume a dataset if you use
the new controls from Visual Studio and use them in Local mode but I don't
really think that is necessary. If all the databases on are the same server
you just join the tables together. Personally I would do the joining in a
stored procedure. If you databases are on different servers then you can use
linked servers. Performance wise you shouldn't join distributed tables. In a
stored procedure I would bring the data over to a temp table and join with
that.
But for you case, a sub report is very easy and should work no problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
Anyway, this is much less of a Reporting Services issue that a straight
database issue.
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:3E01992A-6720-4646-93D1-CC03ADC449F6@.microsoft.com...
> Hi everyone,
> I was reading this post and it is along the lines of what I am looking to
> do
> and wanted to verify sub reports will work. We do not have SSRS yet but
> have
> it as a strong contender for our next reporting solution. We hope to make
> the decision in the next few weeks and this is one area that we are held
> up
> on. I know Crystal will do this for us, but we are hoping SSRS will do
> it.
> We use SQL exclusively as our back end, and we are upgrading to 2005. We
> have our data for reports coming from multiple databases within SQL. As a
> result, we need to be able to gather information from database A, database
> B,
> etc and incorporate the elements using some report parameters and database
> parameters all one one report.
> As a simple example we may have Customer names in Database A, and the
> addresses to those customers in Database B, and the phone numbers to the
> customers in Database C. When the report runs it will need to place all
> of
> them on together in a tabular format so the customer name, address, and
> phone
> number all line up accordingly. In addition, the user will be able to
> search
> by any of these elements to get back one result set of all information.
> Is all of this possible with SSRS 2005? If so is sub reports the best way
> to accomplish this? We will be providing a solution for our applications
> that provides an ADO.NET dataset so our applications can see the different
> databases. Based on the tight integration to SQL Server, I don't image
> SSRS
> could connect to this dataset as well.
> Thanks for your assistance.
> Brian G
>
> "Bruce L-C [MVP]" wrote:
>> No problem. For a certain set of problems Sub reports are really the best
>> and
>> sometimes only way to solve the problem. Note that you can even put a
>> sub report into an empty field of a table on the report.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
>> news:2776A628-1C97-4E02-9E3E-D7683DB46652@.microsoft.com...
>> > Thanks Bruce. Everything works great. My apologies for the evident
>> > frustration in my first post.
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> You are missing a key point. Except for testing you don't ever use the
>> >> subreport by itself. It is always called as a subreport. Note that you
>> >> can
>> >> hide the subreport in list view so the user never sees it (this is
>> >> done
>> >> in
>> >> the property tab in report manager for the report)
>> >>
>> >> The report you will use as a subreport will have a report parameter
>> >> that
>> >> is
>> >> tied to a query parameter for the report.
>> >>
>> >> I assume you have a 1-M (although this works for 1-1 as well)
>> >> relationship
>> >> going on here.
>> >>
>> >> I think what you should do is back up and do a test. Create a very
>> >> simple
>> >> report and subreport doing as I mention and just try it. Subreports
>> >> are a
>> >> very important part of RS and to use RS to its fullest you need to
>> >> understand how to use them.
>> >>
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in
>> >> message
>> >> news:7EA2011F-530F-4343-99D3-67B0C990D45C@.microsoft.com...
>> >> > Thanks for your prompt reply Bruce.
>> >> >
>> >> > How do I create a parameter that does not prompt me to input a
>> >> > value?
>> >> > I
>> >> > don't want a report for a specific userID, I want my report to
>> >> > contain
>> >> > all
>> >> > userIDs. Are you talking about a report parameter or a dataset
>> >> > parameter?
>> >> >
>> >> > Thanks.
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Subreports will work (or it sure seems that way to me).
>> >> >>
>> >> >> Create the subreport (which is really just a report with a
>> >> >> parameter).
>> >> >> The
>> >> >> report that will be the subreport would have a parameter called
>> >> >> UserID.
>> >> >> Create and test the report separately. Then drag and drop onto the
>> >> >> first
>> >> >> report. Do a right mouse click on the subreport, parameters and
>> >> >> then
>> >> >> set
>> >> >> the
>> >> >> report parameter for the subreport to the field userID.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >>
>> >> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
>> >> >> >I have seen post regarding this topic before, but none have given
>> >> >> >a
>> >> >> >clear
>> >> >> >or
>> >> >> > satisfactory answer.
>> >> >> >
>> >> >> > I understand that multiple data sources cannot be directly
>> >> >> > linked.
>> >> >> > This
>> >> >> > alone seems to be a major limitation to this product!
>> >> >> >
>> >> >> > The standard answer seems to be to use subreports. This does not
>> >> >> > work
>> >> >> > in
>> >> >> > my
>> >> >> > case as my report does not utilize any parameters. I want to see
>> >> >> > all
>> >> >> > records
>> >> >> > from the one data set with userID linked to userID in the second
>> >> >> > data
>> >> >> > set
>> >> >> > which comes from a totally different data source. The first data
>> >> >> > source
>> >> >> > is
>> >> >> > Oracle the second is Fox Pro. Can anyone offer suggestions other
>> >> >> > than
>> >> >> > to
>> >> >> > buy
>> >> >> > Crystal/Business Objects?
>> >> >> >
>> >> >> > Thanks in advance.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Hello All,
I've recently began using MS Reporting Services and I've got a
situation where, I have different users needing to access the same
report (rdl) but from different databases?
Ideally I would want to have this one report pointing to different
databases dynamically.
Do you know how I would go about setting this up? Multiple reports
pointing to different datasources? Passing a parameter which
determines a specific datasource?
Thanks for your help in advance
Bruce L-C [MVP] wrote:
> Subreports are an easy way to do it. You can consume a dataset if you use
> the new controls from Visual Studio and use them in Local mode but I don't
> really think that is necessary. If all the databases on are the same server
> you just join the tables together. Personally I would do the joining in a
> stored procedure. If you databases are on different servers then you can use
> linked servers. Performance wise you shouldn't join distributed tables. In a
> stored procedure I would bring the data over to a temp table and join with
> that.
> But for you case, a sub report is very easy and should work no problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> Anyway, this is much less of a Reporting Services issue that a straight
> database issue.
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:3E01992A-6720-4646-93D1-CC03ADC449F6@.microsoft.com...
> > Hi everyone,
> >
> > I was reading this post and it is along the lines of what I am looking to
> > do
> > and wanted to verify sub reports will work. We do not have SSRS yet but
> > have
> > it as a strong contender for our next reporting solution. We hope to make
> > the decision in the next few weeks and this is one area that we are held
> > up
> > on. I know Crystal will do this for us, but we are hoping SSRS will do
> > it.
> >
> > We use SQL exclusively as our back end, and we are upgrading to 2005. We
> > have our data for reports coming from multiple databases within SQL. As a
> > result, we need to be able to gather information from database A, database
> > B,
> > etc and incorporate the elements using some report parameters and database
> > parameters all one one report.
> >
> > As a simple example we may have Customer names in Database A, and the
> > addresses to those customers in Database B, and the phone numbers to the
> > customers in Database C. When the report runs it will need to place all
> > of
> > them on together in a tabular format so the customer name, address, and
> > phone
> > number all line up accordingly. In addition, the user will be able to
> > search
> > by any of these elements to get back one result set of all information.
> >
> > Is all of this possible with SSRS 2005? If so is sub reports the best way
> > to accomplish this? We will be providing a solution for our applications
> > that provides an ADO.NET dataset so our applications can see the different
> > databases. Based on the tight integration to SQL Server, I don't image
> > SSRS
> > could connect to this dataset as well.
> >
> > Thanks for your assistance.
> > Brian G
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> No problem. For a certain set of problems Sub reports are really the best
> >> and
> >> sometimes only way to solve the problem. Note that you can even put a
> >> sub report into an empty field of a table on the report.
> >>
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in message
> >> news:2776A628-1C97-4E02-9E3E-D7683DB46652@.microsoft.com...
> >> > Thanks Bruce. Everything works great. My apologies for the evident
> >> > frustration in my first post.
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> You are missing a key point. Except for testing you don't ever use the
> >> >> subreport by itself. It is always called as a subreport. Note that you
> >> >> can
> >> >> hide the subreport in list view so the user never sees it (this is
> >> >> done
> >> >> in
> >> >> the property tab in report manager for the report)
> >> >>
> >> >> The report you will use as a subreport will have a report parameter
> >> >> that
> >> >> is
> >> >> tied to a query parameter for the report.
> >> >>
> >> >> I assume you have a 1-M (although this works for 1-1 as well)
> >> >> relationship
> >> >> going on here.
> >> >>
> >> >> I think what you should do is back up and do a test. Create a very
> >> >> simple
> >> >> report and subreport doing as I mention and just try it. Subreports
> >> >> are a
> >> >> very important part of RS and to use RS to its fullest you need to
> >> >> understand how to use them.
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:7EA2011F-530F-4343-99D3-67B0C990D45C@.microsoft.com...
> >> >> > Thanks for your prompt reply Bruce.
> >> >> >
> >> >> > How do I create a parameter that does not prompt me to input a
> >> >> > value?
> >> >> > I
> >> >> > don't want a report for a specific userID, I want my report to
> >> >> > contain
> >> >> > all
> >> >> > userIDs. Are you talking about a report parameter or a dataset
> >> >> > parameter?
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Subreports will work (or it sure seems that way to me).
> >> >> >>
> >> >> >> Create the subreport (which is really just a report with a
> >> >> >> parameter).
> >> >> >> The
> >> >> >> report that will be the subreport would have a parameter called
> >> >> >> UserID.
> >> >> >> Create and test the report separately. Then drag and drop onto the
> >> >> >> first
> >> >> >> report. Do a right mouse click on the subreport, parameters and
> >> >> >> then
> >> >> >> set
> >> >> >> the
> >> >> >> report parameter for the subreport to the field userID.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >>
> >> >> >> "disappointed" <disappointed@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:02209EB4-5568-4743-BA57-2EF0B4C4B33D@.microsoft.com...
> >> >> >> >I have seen post regarding this topic before, but none have given
> >> >> >> >a
> >> >> >> >clear
> >> >> >> >or
> >> >> >> > satisfactory answer.
> >> >> >> >
> >> >> >> > I understand that multiple data sources cannot be directly
> >> >> >> > linked.
> >> >> >> > This
> >> >> >> > alone seems to be a major limitation to this product!
> >> >> >> >
> >> >> >> > The standard answer seems to be to use subreports. This does not
> >> >> >> > work
> >> >> >> > in
> >> >> >> > my
> >> >> >> > case as my report does not utilize any parameters. I want to see
> >> >> >> > all
> >> >> >> > records
> >> >> >> > from the one data set with userID linked to userID in the second
> >> >> >> > data
> >> >> >> > set
> >> >> >> > which comes from a totally different data source. The first data
> >> >> >> > source
> >> >> >> > is
> >> >> >> > Oracle the second is Fox Pro. Can anyone offer suggestions other
> >> >> >> > than
> >> >> >> > to
> >> >> >> > buy
> >> >> >> > Crystal/Business Objects?
> >> >> >> >
> >> >> >> > Thanks in advance.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>