Hi Al…thought I'd replied to this, but I guess I killed my browser without pressing Post…doh! 1. apply-templates will very likely have better performance than for-each - there's more scope for the XSLT processor to do optimisations, as apply-templates is a more abstract operation. 2. I've used Michael Kay's XSLT and XPath books, but I think Jeni Tennison's Beginning XSLT would be appropriate for what you want... Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p CodeProject MVP for 2010 - who'd'a thunk it!

Thanks for this - I had a look and decided it was a bit too involved for a demo - I've gone with option 3 (fake it!) for now, so I can get back to my main project! Cheers, Al

Oh and as for changes between 6 & 7 - i doubt it. best thing would be to search on technet etc for "whats new IIS" or something Neonlight

Thanks for this Dave - it definitely seems to be pointing in the right direction.

I'm suspicious of your Content-Length. I believe SOAP won't see anything past the 115th character of your request, which is a lot less than all of it.

I use ZedGraph.

Woohoo! Yup - the default locations were blank (dunno where it was getting them from before :doh: ) Changed and successful - did not even have to restart SQL server agent or anything. Cheers Mike! :rose:

use sonia create table stud(roll int identity(10,2),name varchar) insert into stud values('A') insert into stud values('B') select * from stud **IDENTITY(10,2) --> 10 is the initial value 2 is the number by which the value is to be incremented. U can also decrement the value.

Neophyte30 wrote: I didn't find/see a link to this documentation DateTime.TryParse() has an overload that takes a IFormatProvider parameter and puts you in charge of what is acceptable and what is not. :) Luc Pattyn [Forum Guidelines] [My Articles] This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.

OK - "problem" solved. It was a viewstate issue. Some idiot :-O had discovered that disabling the viewstate on a slow-loading page improved performance. And decided to do the same thing on every page. Including the Master Pages. Which is why enabling/disabling the viewstate on the content page did pretty much zip. My apologies for wasting your valuable time. Of course had I been documenting my modifications as I went along, I might have twigged a little quicker...

Resolved by deleting the files from the server and re-publishing. Still not sure where the old files were being cached.

You can also do this in a stylesheet if you don't care too much about the bandwidth. The benefits to this approach are that the text is trimmed at the appropriate position as the client lays it out. To be honest I sincerely doubt there is any real gain to be made trimming the string on the database vs in the code behind... (unless we are talking massive amounts of text) ;) Mark Churchill Director Dunn & Churchill Free Download: Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.

I got around this problem for the prototype demo by not having enough data to require scrolling! For the production version I will probably create a custom gridview inheriting from Gridview, or dolly up a Repeater with some sorting capabilities. However, I'm still curious as to what would cause this. I assume it's client side (IE only - not tried in FF) as I don't see any postback or page refresh. Any thoughts?

//Works like a charm! Ta muchly! // :-D Ignore my previous response! Having written and executed my little applet, I didn't get any results. Which was odd, because I knew there were at least a few of these rogue files. On further investigation, it appears that the string says they are 1.4 - but are being reported on the properties-pdf tab as version 1.5. I'll dig a little deeper and get back to you. modified on Friday, January 11, 2008 8:14:52 AM