changing the server used by a report

hopefully have better luck with this.

I have two servers running the same database for two locations, I have a site setup to report for one of them and I want to make it report for both based on what location a person is in.

I have it working when there are no parameters, however as soon as you enter parameters into the mix it breaks.

here is what I use to do it when no parameters are required.

CrystalReportSource1.ReportDocument.DataSourceConnections[0].SetConnection(myConnectionInfo.ServerName, myConnectionInfo.DatabaseName, false);

CrystalReportSource1.ReportDocument.DataSourceConnections[0].SetLogon(myConnectionInfo.UserID, myConnectionInfo.Password);

I tried to put this in various locations, before the parameters are read, after reading but before setting, after everything.
Even before the report is loaded!

all gave me an error on the report.

I also tried to grab the parameter definitions, then set these and then copy the definitions back and that failed, it was read only.

Any ideas?

ThanksNM - threw in a verifydatabase on the report document and all is well.

Changing Remote Schemas

Running Win 2K & SQL 2K
I have 15 remote locations that all have transactional
publications that are pushed to my corp. office. I need
to add a field to one of the tables that are replicated
to the corp. office at all 15 locations. So my question
is this...
What is the easiest way of accomplishing this? I know I
can add a field to a published table and the change in
schema will be replicated to the subscriber, but what
about when there are 15 publishers and only one
subscriber? How will SQL handle this?
Any help is appreciated.
Larry...
for one publisher to many susbcribers you use sp_repladdcolumn or sp_repldropcolumn.
however you have 15 publishers replicating to a single subscriber. You have probably done a no-sync subscription as well.
I suggest the best approach would be to drop the 14 or the 15 subscriptions. Make the changes on one Publisher, when the Susbcriber has received the change and the smoke settles, dust clears, make the change on the remaining 14 subscribers, and then resyn
c again using the nosync option.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Changing DB locations in production

Can't seem to find the answer to this one.
Anyway, I have a report class that several developers use for reporting.
Each developer has his own DB.
The report class uses the web services for connecting/viewing.
What I want to do is be able for each developer to pass a connection string
or something that will point a shared report to his DB. I really don't want
to create copies of the reports.
Plus, when all production is done we may have hundreds of clients using one
report and each one would need their own DB.
Thanks for any suggestions!
cbmeeks*BUMP*
Sorry to bump but this is starting to become a problem here.
Thanks for any help!
cbmeeks
"cbmeeks" wrote:
> Can't seem to find the answer to this one.
> Anyway, I have a report class that several developers use for reporting.
> Each developer has his own DB.
> The report class uses the web services for connecting/viewing.
> What I want to do is be able for each developer to pass a connection string
> or something that will point a shared report to his DB. I really don't want
> to create copies of the reports.
> Plus, when all production is done we may have hundreds of clients using one
> report and each one would need their own DB.
> Thanks for any suggestions!
> cbmeeks