Search results

yes, make an html template and use the file system object to read the html text of that template to a stream and save it as a string. use that string as the body of the email.

use the msxmldom object instead http://www.perfectxml.com/msxmlDOM.asp#3 get it as a string and then you have your way with it.

http://www.aspfaq.com/show.asp?id=2026

when in asp you must use server.createobject Set myMail=Server.CreateObject("CDO.Message")

yes. All you are doing is modifying the font.

this is not the same error message but it could be another related issue http://support.microsoft.com/kb/820631

give an id to your button so it doesn't apply to all input elements.. and then make a css class for it with the style of font-family=fontname;

I bet it has to do with the collection size in bytes. You might have to limit the selection to like 300 at a time until a solution can be found.

hard to say without seeing what readtag does, but in this view, we aren't seeing any file exists checking.. are you doing any checks on this? have you debugged and stepped through to make sure that the full path is going to the function ok?

set ASP.NET USER and IUSR_ to have modify rights to the FOLDER that the db is in. Make sure these rights propagate down to child objects.

I use www.webhost4life.com

can't be done with asp script without an activex control or some other client side control.

not entirely correct. The proper way is to use quotes, not apostrophe's Response.write("<img src=""boat.gif"" alt=""Big Boat"">")

http://www.learn2asp.net/campaign.aspx?refID=cmp-01

That usually means that the object hasn't been installed on the server you're trying to create it from or you're object reference is incorrect.

Been there.. I actually got so tired of buying books that were not hitting on the points that I needed to wrap my head around that I just went to videos instead. Now those books make more sense. http://www.microsoft.com/events/series/msdnwebdev.mspx...

A lot of the drag and drop things out there like table adapters generally break basic rules of coupling by bringing your DATA layer up to your presentation layer which is a big no no. They're great for proto-typing an application so you can say.. lets do this and it should do this and look like...

Views are like "virtual" tables if you will. They are good for "hiding" things from developers.. Lets say a devleoper wanted to get Personnel info for a front end display.. the DBA can refuse access to the table directly and offer a view that only shows pertinant information to the developers...

When I showed up my first day at College (we call it College in the US), I wasn't scared one bit. I was a bit frustrated at the disorganization of everything but I showed up like I owned it and people ended up asking me what to do. I ended up making a lot friends on the first day because I was...

set ANSI_NULLS ON set QUOTED_IDENTIFIER ON go Create PROCEDURE [dbo].[InsertOrder] ( @CustomerID Int, @PaymentTypeID Int, @PickupLocationID Int, @NumberOfPayrollDeducts Int ) AS BEGIN TRANSACTION Set NoCount On Declare @OrderID Int -- INSERT the new Order INSERT INTO...