Friday, March 30, 2012
linking from one report to another
I've build my own report viewer app in an aspx project. This is made
up using frames - top frame for navigation, bottom frame for viewing
reports. One of my reports links to another report. I have this
working, but have 2 issues...
1. When I click on the link it loads the new report in the entire
window - overriding my frame. This also prints the entire url in the
address bar of the browser, parameters and all. I need to load it in
the correct frame in the frameset.
2. Hovering over the link to the report shows the url in the status
bar. I don't want this to happen either.
Can anybody help with a solution for either of these'
Thanks,
Gearoidok, i solved the first part of this by adding -
&rc:LinkTarget=frameName - to the url string of the report which links
to the graph. All reports which stem from the base report inherit the
same properties.
Now just to hide urls in the status bar...
ghealy@.gmail.com (Gear?id) wrote in message news:<173a60fb.0409200812.75da1f0a@.posting.google.com>...
> Hi
> I've build my own report viewer app in an aspx project. This is made
> up using frames - top frame for navigation, bottom frame for viewing
> reports. One of my reports links to another report. I have this
> working, but have 2 issues...
> 1. When I click on the link it loads the new report in the entire
> window - overriding my frame. This also prints the entire url in the
> address bar of the browser, parameters and all. I need to load it in
> the correct frame in the frameset.
> 2. Hovering over the link to the report shows the url in the status
> bar. I don't want this to happen either.
> Can anybody help with a solution for either of these'
> Thanks,
> Gearoid
Wednesday, March 28, 2012
Linking between two databases
Is it posable to link between two diferent Databases? I am putting membership on my visual studios website which by default builds it's own database. I am then building a database for our products and services. I don't want to have to recreate all the client inforation that I already have in the default member database. But I don't think I want to put all the other info in the membershipp database.
Thanks for any help and advice
Ed
Hi,
you can either access your database by using three part names:
SELECT * FROM Database.Schema.ObjectName [Schema is called owner in SQL Server 2000]
or (but this implies the above one) creating view based on the table and syntax information above.
You have to keep in mind that you have to deal with the security in any way. There is a feature called crossdatabase ownership chain which would apply if activated to grant the user the rights in the destination database if the owner is the same across the databases and he has access in the current database to the object (like a view).
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
sqlWednesday, March 21, 2012
servers and sp_executeSQL
I am trying to do something like the following within a Stored Procedure but have also tried it on its own within a batch:
--
go
Declare @.MySQL nvarchar(500)
@.MySQL = 'Select * from openquery(borders, ''Select * from
dba.organise'')'
exec sp_executeSQL @.MySQL
go
--
then I get Error 7405 'Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection...' I tried setting these in a SQL batch before the one above. Various sources say that you should set these before you create procedure but as you can see above I am not doing this within a create procedure - is it something to do with the sp_executeSQL ?? Help!!!EXEC and sp_executeSQL run on seperate threads so include the set statments in your string
@.MySQL = 'set ANSI_NULLS on
set ANSI_WARNINGS on
Select * from openquery(borders, ''Select * from dba.organise'')'
exec(@.MySQL)
Also, I have found that including the database name in the table reference will eliminate headaches.|||Thanks Paul - What I eventually did was this:
set ansi_nulls on
set ansi_warnings on
go
create procedure ....
... putting it in the SQL statement worked in Query Analyzer but not when it was within the stored procedure.
Thanks for the quick reply!
Regards
Anna|||I would suggest doing the SETs inside the sp, that way if someone extracts the code from your server and recompiles you will still have the correct environment for you linked server query|||Hi Paul,
I did try that but I couldn't seem to get that to work.
Cheers
Anna