Non-Report Hyperlinks on Report Manager Home Page?

Is it possible to add hyperlinks to the Report Manager Home Page that link to other aspx pages? I have created some associated data entry aspx pages that I want to enable access to from the Report Manager Home Page (if possible).

Thanks!

It isn't...maybe you could run it inside an IFRAME, surrounded by other UI (including "your" hyperlinks)?|||

pittpanther wrote:

Is it possible to add hyperlinks to the Report Manager Home Page that link to other aspx pages? I have created some associated data entry aspx pages that I want to enable access to from the Report Manager Home Page (if possible).

Thanks!

Why not just create an "index" aspx page that would have links to reports similar to report manager? You could have this index page in the same project as the associated data entry aspx pages.

It seems to me that you're thinking about it backwards.

|||

Thanks for the replies...

The end user is already fairly comfortable with the Report Manager front end, so I am kind of stuck with it as my launching point.

The only thing I have come up with is an "empty" report accessible from the main folder that only includes the hyperlinks for the "Data Entry" aspx pages. A little kludgy though.

|||Russell - I am not familiar with an IFRAME... could you elaborate a little more?sql

Non-Report Hyperlinks on Report Manager Home Page?

Is it possible to add hyperlinks to the Report Manager Home Page that link to other aspx pages? I have created some associated data entry aspx pages that I want to enable access to from the Report Manager Home Page (if possible).

Thanks!

It isn't...maybe you could run it inside an IFRAME, surrounded by other UI (including "your" hyperlinks)?|||

pittpanther wrote:

Is it possible to add hyperlinks to the Report Manager Home Page that link to other aspx pages? I have created some associated data entry aspx pages that I want to enable access to from the Report Manager Home Page (if possible).

Thanks!

Why not just create an "index" aspx page that would have links to reports similar to report manager? You could have this index page in the same project as the associated data entry aspx pages.

It seems to me that you're thinking about it backwards.

|||

Thanks for the replies...

The end user is already fairly comfortable with the Report Manager front end, so I am kind of stuck with it as my launching point.

The only thing I have come up with is an "empty" report accessible from the main folder that only includes the hyperlinks for the "Data Entry" aspx pages. A little kludgy though.

|||Russell - I am not familiar with an IFRAME... could you elaborate a little more?

Noise Words

http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely how to
get SQL Server to ignore noise words in the query, BOL's discussion on noise
words is all nice except things don't seem as they appear.
Right from BOL:
Important:
If you edit a noise-word file, you must repopulate the full-text catalogs
before the changes will take effect.
Yes, the DBA has a choice in the matter. No, wait...I made changes,
repopulated the index, and I'm still not getting the results I want.
There are words in the $SQL_Server_Install_Path\Microsoft SQL
Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
words. When I remove them and repopulate the index, I still get tagged for
"Informational: The full-text search condition contained noise word(s)."
Is there a literal difference from words of BOL "repopulate the full-text
catalogs" and the context menu item "Start full Population"? I know I must
be overlooking something. Can I seriously edit the noise words, or is it a
tease?
-Dan
Please forgive me, I did discover that rebuilding the Catelog is much
different than repopulating the indexes. Maybe the BOL could differentiate
this better since Index manuveres can be achieved thru context menus and
catelogs have to be rebuilt via a ALTER FULLTEXT CATALOG statement. not
real clear in the docs
-Dan
"Dan Davis" wrote:

> http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely how to
> get SQL Server to ignore noise words in the query, BOL's discussion on noise
> words is all nice except things don't seem as they appear.
> Right from BOL:
> Important:
> If you edit a noise-word file, you must repopulate the full-text catalogs
> before the changes will take effect.
> Yes, the DBA has a choice in the matter. No, wait...I made changes,
> repopulated the index, and I'm still not getting the results I want.
> There are words in the $SQL_Server_Install_Path\Microsoft SQL
> Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
> words. When I remove them and repopulate the index, I still get tagged for
> "Informational: The full-text search condition contained noise word(s)."
>
> Is there a literal difference from words of BOL "repopulate the full-text
> catalogs" and the context menu item "Start full Population"? I know I must
> be overlooking something. Can I seriously edit the noise words, or is it a
> tease?
> -Dan
|||Hi Dan
There is a .fulltext newsgroup. You might have better luck posting your
questions there.
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Dan Davis" <In_Finite@.news.postalias> wrote in message
news:9F9E5E9A-1A7F-484A-98B3-E3E8F5C95F27@.microsoft.com...[vbcol=seagreen]
> Please forgive me, I did discover that rebuilding the Catelog is much
> different than repopulating the indexes. Maybe the BOL could
> differentiate
> this better since Index manuveres can be achieved thru context menus and
> catelogs have to be rebuilt via a ALTER FULLTEXT CATALOG statement. not
> real clear in the docs
> -Dan
> "Dan Davis" wrote:

Noise Words

http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely how t
o
get SQL Server to ignore noise words in the query, BOL's discussion on noise
words is all nice except things don't seem as they appear.
Right from BOL:
Important:
If you edit a noise-word file, you must repopulate the full-text catalogs
before the changes will take effect.
Yes, the DBA has a choice in the matter. No, wait...I made changes,
repopulated the index, and I'm still not getting the results I want.
There are words in the $SQL_Server_Install_Path\Microsoft SQL
Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
words. When I remove them and repopulate the index, I still get tagged for
"Informational: The full-text search condition contained noise word(s)."
Is there a literal difference from words of BOL "repopulate the full-text
catalogs" and the context menu item "Start full Population"? I know I must
be overlooking something. Can I seriously edit the noise words, or is it a
tease?
-DanPlease forgive me, I did discover that rebuilding the Catelog is much
different than repopulating the indexes. Maybe the BOL could differentiate
this better since Index manuveres can be achieved thru context menus and
catelogs have to be rebuilt via a ALTER FULLTEXT CATALOG statement. not
real clear in the docs
-Dan
"Dan Davis" wrote:

> http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely how
to
> get SQL Server to ignore noise words in the query, BOL's discussion on noi
se
> words is all nice except things don't seem as they appear.
> Right from BOL:
> Important:
> If you edit a noise-word file, you must repopulate the full-text catalogs
> before the changes will take effect.
> Yes, the DBA has a choice in the matter. No, wait...I made changes,
> repopulated the index, and I'm still not getting the results I want.
> There are words in the $SQL_Server_Install_Path\Microsoft SQL
> Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
> words. When I remove them and repopulate the index, I still get tagged fo
r
> "Informational: The full-text search condition contained noise word(s)."
>
> Is there a literal difference from words of BOL "repopulate the full-text
> catalogs" and the context menu item "Start full Population"? I know I mus
t
> be overlooking something. Can I seriously edit the noise words, or is it
a
> tease?
> -Dan|||Hi Dan
There is a .fulltext newsgroup. You might have better luck posting your
questions there.
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Dan Davis" <In_Finite@.news.postalias> wrote in message
news:9F9E5E9A-1A7F-484A-98B3-E3E8F5C95F27@.microsoft.com...[vbcol=seagreen]
> Please forgive me, I did discover that rebuilding the Catelog is much
> different than repopulating the indexes. Maybe the BOL could
> differentiate
> this better since Index manuveres can be achieved thru context menus and
> catelogs have to be rebuilt via a ALTER FULLTEXT CATALOG statement. not
> real clear in the docs
> -Dan
> "Dan Davis" wrote:
>

Noise Words

http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely how to
get SQL Server to ignore noise words in the query, BOL's discussion on noise
words is all nice except things don't seem as they appear.
Right from BOL:
Important:
If you edit a noise-word file, you must repopulate the full-text catalogs
before the changes will take effect.
Yes, the DBA has a choice in the matter. No, wait...I made changes,
repopulated the index, and I'm still not getting the results I want.
There are words in the $SQL_Server_Install_Path\Microsoft SQL
Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
words. When I remove them and repopulate the index, I still get tagged for
"Informational: The full-text search condition contained noise word(s)."
Is there a literal difference from words of BOL "repopulate the full-text
catalogs" and the context menu item "Start full Population"? I know I must
be overlooking something. Can I seriously edit the noise words, or is it a
tease?
-DanPlease forgive me, I did discover that rebuilding the Catelog is much
different than repopulating the indexes. Maybe the BOL could differentiate
this better since Index manuveres can be achieved thru context menus and
catelogs have to be rebuilt via a ALTER FULLTEXT CATALOG statement. not
real clear in the docs
-Dan
"Dan Davis" wrote:
> http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely how to
> get SQL Server to ignore noise words in the query, BOL's discussion on noise
> words is all nice except things don't seem as they appear.
> Right from BOL:
> Important:
> If you edit a noise-word file, you must repopulate the full-text catalogs
> before the changes will take effect.
> Yes, the DBA has a choice in the matter. No, wait...I made changes,
> repopulated the index, and I'm still not getting the results I want.
> There are words in the $SQL_Server_Install_Path\Microsoft SQL
> Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
> words. When I remove them and repopulate the index, I still get tagged for
> "Informational: The full-text search condition contained noise word(s)."
>
> Is there a literal difference from words of BOL "repopulate the full-text
> catalogs" and the context menu item "Start full Population"? I know I must
> be overlooking something. Can I seriously edit the noise words, or is it a
> tease?
> -Dan|||Hi Dan
There is a .fulltext newsgroup. You might have better luck posting your
questions there.
--
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Dan Davis" <In_Finite@.news.postalias> wrote in message
news:9F9E5E9A-1A7F-484A-98B3-E3E8F5C95F27@.microsoft.com...
> Please forgive me, I did discover that rebuilding the Catelog is much
> different than repopulating the indexes. Maybe the BOL could
> differentiate
> this better since Index manuveres can be achieved thru context menus and
> catelogs have to be rebuilt via a ALTER FULLTEXT CATALOG statement. not
> real clear in the docs
> -Dan
> "Dan Davis" wrote:
>> http://msdn2.microsoft.com/en-us/library/ms345119.aspx explains nicely
>> how to
>> get SQL Server to ignore noise words in the query, BOL's discussion on
>> noise
>> words is all nice except things don't seem as they appear.
>> Right from BOL:
>> Important:
>> If you edit a noise-word file, you must repopulate the full-text catalogs
>> before the changes will take effect.
>> Yes, the DBA has a choice in the matter. No, wait...I made changes,
>> repopulated the index, and I'm still not getting the results I want.
>> There are words in the $SQL_Server_Install_Path\Microsoft SQL
>> Server\MSSQL.1\MSSQL\FTDATA\ noise files that I don't agree with as noise
>> words. When I remove them and repopulate the index, I still get tagged
>> for
>> "Informational: The full-text search condition contained noise word(s)."
>>
>> Is there a literal difference from words of BOL "repopulate the full-text
>> catalogs" and the context menu item "Start full Population"? I know I
>> must
>> be overlooking something. Can I seriously edit the noise words, or is it
>> a
>> tease?
>> -Dan