Well, maybe I was a bit misleading. The book actually covers a lot more besides only stored procedures. So there are only a few chapters devoted to stored procedures alone. It covers extended stored procedures, administrative stored procedures in sql server, and the basics about writing stored procedures. So if you only want to focus on stored procedures, you might want to try another book.

The Guru's Guide to SQL Server Stored Procedures, XML, and HTML[^] By Ken Henderson That's the one I have, and I like it. Regards, Jeffry

62.85 points, but that's because I got 5 points for telling I found the site through CodeProject :)

I think you need this: http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx#00000153[^] HTH, Jeffry

Roger J wrote: so why are the components still being sold? (oke in your case its abit different since you actually did make the free version somewhat different with the watermark) but for c1 , why do they still sell those compoentns? Why is (almost) everyone are some people so paranoid about it? :suss: :confused: I think it's great! I downloaded the resource kit, registered the components and I see no trials, nag screens or whatever. The "powered by Dundas" is very small and doesn't bother me at all. You get a ONE TIME free version of the components, no upgrades (except for C1, which includes a one time upgrade). So if you like the components, you might want to buy upgrades. That's the catch, if you can call it a catch. :) So I guess the sales will drop at the moment because of this action, but hopefully/probably they will rise because of people wanting to buy upgrades, etc. Just download it, try it and see for yourselves.

My perception of the USA is this: I don't think the USA really exists, it's something they made up in Hollywood....:cool: Looking at it that way, it all makes sense. ;)

You cannot serialize a datareader as far as I know. It doesn't implement the ISerializable interface. However, it does inherit from MarshalByRefObject so you could return a reference to the datareader from your webservice. So you could do something like this: SqlDataReader dr = myWebService.GetDatareader(); Just be sure to close the connection when you're done with the datareader! Depending on your needs, you might be better of with a DataSet, e.g. if you need to hold on to the data for a while. HTH, Jeffry