You should use regular expressions, which are stored in System.Text.RegularExpressions namespace. For example string header = (Your header),match=""; Regex r = new Regex("Subject:.*"); Match m=r.Match(header); if(m.Success){ match = m.Value; } Now match contains the line beginning with "Subject:".

Thanks Dave. :) I am now cracking my head to solve the problem. My server default date is US format, and the sql server as well. However, when users enter data through the web, they will enter 18/11/2004 (dd/mm/yyyy), I am trying to convert it and store in sql server using 11/18/2004 (mm/dd/yyyy). I wanted to do in dynamic way, hence I think globalization method in .Net is the solution. I try to parse by US format at first, then UK format... however end up still having error. How shall I deal with this? :sigh: Thanks! regards, vic

reference it in your project. ObjCommon oc = new ObjCommon() ??? This demographic will quite happily click on shiny things however:laugh: Found on Bash.org [erno] hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is.

check application's WEB.CONFIG and try increasing the session timeout... by default it is 20 minutes. good luck ------------------- Therez No Place like ... 127.0.0.1

The following works for me: int min = 1000000, max = 9999999; Random r = new Random(); for(int i = 0; i < 5; i++) { Console.WriteLine(r.Next(min, max)); } - Nick Parker My Blog | My Articles

Heath Stewart wrote: Exciting! I've been through tornados having been from the midwest, but this is a new experience. I had a lot of interest in volcanoes (and earthquakes) when I was younger (did a fair share more than just "class projects" on them) so this will be fun to see in person. If I get a chance I'll be taking some pics. Awsome! :-D I'm so jealous! I've had that same, call it morbid, curiosity about how these things work and still have it to this day. I've been within 500 feet of a tornado before, BUT COULDN'T SEE IT! because it was heavily rain-wrapped. All we saw, looking through the 8 foot tall plate glass windows in the front of the store ;P, were roofs being torn off buildings ... what a let-down that was. I've even had the pleasure of watching empty Coke cans slide back and forth acrossed my desk during earthquakes in and around South-East Michigan. I know, it's not an earthquake mecca and they're weak by Pacific Coast standards, but it's still pretty funny to try and balance on one foot while putting jeans on during an earthquake (1986 - epicenter in middle of Lake Erie). If Mt St Helens blows again, we want pictures! LOTS of pictures! Setup a webcam if you have to! Who knows if the one at the Johnston Ridge Observatory[^] will be working if/when it does decide to erupt. and now, back to our show... --------8<-------------------------- I agree with your assessment of the speed of persisting Session info to an SQL server. It's as flexible a solution as your going to get, but it does tend to be a little slow. I've installed the SQL state server package that comes with, I can't remember which or where, but I think, ASP.NET or Visual Studio .NET Enterprise. I've thought about both single and multiple server session state caching schemes. A single server solution is easy to implement, but has the downfall of not being scalable to support say, 15 IIS servers. Mostly, I've wondered what the benefits, limitations and pitfalls are of a solution consisting of small cluster of servers, no more than 3 to start, each running a "Singleton" component, but sync'ing up their data on a real-time basis. These servers could possibly run behind a single-IP solution to facilitate fault-tolerance. The list of ponderings I've come up with is pretty long... What would be the database s