build your info, pass it back to the client through a javascript
"window.open()" perhaps.

Signature
Curt Christianson
site: http://www.darkfalz.com
blog: http://blog.darkfalz.com
> Hi,
>
[quoted text clipped - 9 lines]
>
> Brian
The first point to make is that mailto: is not covered by internet standards
and is generally considered bad practice for anything other than a simple
"contact me" link. For instance, it won't work if the user uses webmail or
hasn't properly configured the default email client.
specifying the body text as part of the link only works with certain
combinations of browser and mail client (IIRC it works in with IE and
Outlook Express but not Outlook)
my preference would normally be to send the email from the server (in
asp.net use System.Web.Mail). however, this does assume that your server has
access to an smtp server that can send the mail.
if you want to use mailto with dynamically generated text, and
response.redirect doesn't work, my next best guess would be to use something
like:
<body onload='document.location.href="mailto:blah blah<%=the server
generated content"%>'>
I haven't tested it so I don't know if that would work, but if it doesn't, I
can't think of any solution.
Andy
> Hi,
>
[quoted text clipped - 9 lines]
>
> Brian
Brian - 20 Oct 2005 14:07 GMT
Thank you for the heads up on the issues with mailto. These are not an issue
in my case where this will be running in a controlled environment over our
Intranet. An the functionality was explicitly asked for.
After playing around some, I found the hyperlinkbutton works, but it is ugly
and doesn't get displayed the same way that my other buttons are. So I
thought of hiding it and causing a click from code, but there doesn't appear
to be a way to do this.
Anyway, I will have a look at you suggestion and keep digging.
Thanks
Brian
> The first point to make is that mailto: is not covered by internet
> standards and is generally considered bad practice for anything other than
[quoted text clipped - 34 lines]
>>
>> Brian