NooB Scripting Question How to use mailto

I am a noob to sql and asp programming. I am working on a db for the
gaming squad I am a member of. One of the pages I created is a roster
list of all the squad members. Part of this roster is listing each
member's email address. What several people have asked of me is to
make it so the email addresses can be clicked on to open their email
programs, just as html allows the mailto function to work.

Here is a copy of the coding I am currently using:
<td align="center"><font face="Arial"
color="#C0C0C0"><%=rst("email")%></font></td>
This will list the email address of the person, but how do I make it
so the line will function as a mailto command?
The page is saved as an .asp.

Thanks for any advice!

Davedavestrike (davestrike@.nventure.com) writes:
> Here is a copy of the coding I am currently using:
><td align="center"><font face="Arial"
> color="#C0C0C0"><%=rst("email")%></font></td>
> This will list the email address of the person, but how do I make it
> so the line will function as a mailto command?
> The page is saved as an .asp.

Actually, I don't have the slightest idea, nor do I feel to compelled
to have one, since this is an SQL Server forum, and not related to ASP.

But they say ASP has something to do with HTML, in which case I would
try with:

<td align="center"><font face="Arial" color="#C0C0C0">
<A HEF="mailto:%=rst("email")%"><%=rst("email")%></A>
</font></td
But if that does not work (and it probably doesn't) you should look
for an ASP forum.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

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?

non-leaf-level pages and leaf-level pages?

Hi
What is de diferents beetwen non-leaf-level pages and leaf-level pages?
Thanks
Best Regards
CesarThe 'non-leaf level pages are key-value pairs used to navigate down to the
'leaf-level' pages desired.
For a clustered index, the 'leaf-level' pages are where the table data is
actually stored.
For non-clustered indexes, the 'leaf-level' pages contain key-value pairs
directing the search to either the key used in a clustered index, or to a
pointer to the heap where data is stored since it is not clustered.
For a more detailed description, check Books on Line.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Cesar" <hgfdhfg@.jksjn.com> wrote in message
news:%23G8R4l$uGHA.1372@.TK2MSFTNGP04.phx.gbl...
> Hi
> What is de diferents beetwen non-leaf-level pages and leaf-level pages?
> Thanks
> Best Regards
> Cesar
>|||Cesar wrote:
> Hi
> What is de diferents beetwen non-leaf-level pages and leaf-level pages?
> Thanks
> Best Regards
> Cesar
>
Imagine a tree growing in your back yard. Your data (or pointers to
your data) is stored in the leaves of the tree, or at the "leaf level".
To reach those leaves, you have to climb the tree, moving from branch
to branch until you reach the desired leaf. Every time you reach a fork
in the tree, you have to make a decision as to which branch of the fork
you should follow.
The database engine has to do the same thing, only with a binary data
tree. When it reaches a fork in the tree, it has to decide which branch
to take. It makes that decision by looking at data stored at the
"non-leaf level".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy ..
"Tracy McKibben" <tracy@.realsqlguy.com> ha scritto nel messaggio
news:u0w214HvGHA.1372@.TK2MSFTNGP04.phx.gbl...
> Cesar wrote:
> > Hi
> > What is de diferents beetwen non-leaf-level pages and leaf-level pages?
> > Thanks
> >
> > Best Regards
> >
> > Cesar
> >
> >
> Imagine a tree growing in your back yard. Your data (or pointers to
> your data) is stored in the leaves of the tree, or at the "leaf level".
> To reach those leaves, you have to climb the tree, moving from branch
> to branch until you reach the desired leaf. Every time you reach a fork
> in the tree, you have to make a decision as to which branch of the fork
> you should follow.
> The database engine has to do the same thing, only with a binary data
> tree. When it reaches a fork in the tree, it has to decide which branch
> to take. It makes that decision by looking at data stored at the
> "non-leaf level".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Thanks Arnie.
"Arnie Rowland" <arnie@.1568.com> ha scritto nel messaggio
news:eVkyoSAvGHA.3500@.TK2MSFTNGP06.phx.gbl...
> The 'non-leaf level pages are key-value pairs used to navigate down to the
> 'leaf-level' pages desired.
> For a clustered index, the 'leaf-level' pages are where the table data is
> actually stored.
> For non-clustered indexes, the 'leaf-level' pages contain key-value pairs
> directing the search to either the key used in a clustered index, or to a
> pointer to the heap where data is stored since it is not clustered.
> For a more detailed description, check Books on Line.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Cesar" <hgfdhfg@.jksjn.com> wrote in message
> news:%23G8R4l$uGHA.1372@.TK2MSFTNGP04.phx.gbl...
> > Hi
> > What is de diferents beetwen non-leaf-level pages and leaf-level pages?
> > Thanks
> >
> > Best Regards
> >
> > Cesar
> >
> >
>

non-leaf-level pages and leaf-level pages?

Hi
What is de diferents beetwen non-leaf-level pages and leaf-level pages?
Thanks
Best Regards
CesarThe 'non-leaf level pages are key-value pairs used to navigate down to the
'leaf-level' pages desired.
For a clustered index, the 'leaf-level' pages are where the table data is
actually stored.
For non-clustered indexes, the 'leaf-level' pages contain key-value pairs
directing the search to either the key used in a clustered index, or to a
pointer to the heap where data is stored since it is not clustered.
For a more detailed description, check Books on Line.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Cesar" <hgfdhfg@.jksjn.com> wrote in message
news:%23G8R4l$uGHA.1372@.TK2MSFTNGP04.phx.gbl...
> Hi
> What is de diferents beetwen non-leaf-level pages and leaf-level pages?
> Thanks
> Best Regards
> Cesar
>|||Cesar wrote:
> Hi
> What is de diferents beetwen non-leaf-level pages and leaf-level pages?
> Thanks
> Best Regards
> Cesar
>
Imagine a tree growing in your back yard. Your data (or pointers to
your data) is stored in the leaves of the tree, or at the "leaf level".
To reach those leaves, you have to climb the tree, moving from branch
to branch until you reach the desired leaf. Every time you reach a fork
in the tree, you have to make a decision as to which branch of the fork
you should follow.
The database engine has to do the same thing, only with a binary data
tree. When it reaches a fork in the tree, it has to decide which branch
to take. It makes that decision by looking at data stored at the
"non-leaf level".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy ..
"Tracy McKibben" <tracy@.realsqlguy.com> ha scritto nel messaggio
news:u0w214HvGHA.1372@.TK2MSFTNGP04.phx.gbl...
> Cesar wrote:
> Imagine a tree growing in your back yard. Your data (or pointers to
> your data) is stored in the leaves of the tree, or at the "leaf level".
> To reach those leaves, you have to climb the tree, moving from branch
> to branch until you reach the desired leaf. Every time you reach a fork
> in the tree, you have to make a decision as to which branch of the fork
> you should follow.
> The database engine has to do the same thing, only with a binary data
> tree. When it reaches a fork in the tree, it has to decide which branch
> to take. It makes that decision by looking at data stored at the
> "non-leaf level".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Thanks Arnie.
"Arnie Rowland" <arnie@.1568.com> ha scritto nel messaggio
news:eVkyoSAvGHA.3500@.TK2MSFTNGP06.phx.gbl...
> The 'non-leaf level pages are key-value pairs used to navigate down to the
> 'leaf-level' pages desired.
> For a clustered index, the 'leaf-level' pages are where the table data is
> actually stored.
> For non-clustered indexes, the 'leaf-level' pages contain key-value pairs
> directing the search to either the key used in a clustered index, or to a
> pointer to the heap where data is stored since it is not clustered.
> For a more detailed description, check Books on Line.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Cesar" <hgfdhfg@.jksjn.com> wrote in message
> news:%23G8R4l$uGHA.1372@.TK2MSFTNGP04.phx.gbl...
>