Pfew, knowing that lets me sleep better at night ;P WM. What about weapons of mass-construction?

The evaluation edition was completely removed as any new install flags any remnants that needs removing. I was instructed during new install to move my 'Data' to another location which I did. The packages although saved to 'Sql Server' had created 'dtsx' files as well. However, from VS 2005 I can create a package, but cannot see, or access it in the SQL 2005 Management Studio. I wish error messages could have been more friendly [see my comments in the article on SQLCMD]. I am technical writer and I routinely, meticulously document what I do. Here are my recent articles. Thnaks for your fast response. Moving Data from SQL Server 2000 to SQL Server 2005 Querying Databases in SQL Server 2005 SQL2000 Data Transfer is a snap with SQL 2005 On using the SQLCMD in SQL 2005 Server Generating and Hosting a SQL Server Reporting Services Report Using SQL Server 2005 Business Intelligence Development Studio These and other articles may be found at:http://www.angelfire.com/vt2/hodentek/[^]

No, it is used only for informational or warning messages. All errors will raise an exception. We need to graduate from the ridiculous notion that greed is some kind of elixir for capitalism - it's the downfall of capitalism. Self-interest, maybe, but self-interest run amok does not serve anyone. The core value of conscious capitalism is enlightened self-interest. Patricia Aburdene

Hi progload: Wraps have become very popular in Manhattan delis, but this one is really cool. Thanks for the link. After all code reuse is the goal. In case I use this I will definitely reference this one. Thanks Jayaram Krishnaswamy

Interesting, very interesting, indeed. I think these Folders which have long names(some code) are like Blackholes where you dump in these troubled items so that they somehow gets flushed out. If I find out what is happening, I will let you know. Thanks.

There are several ways you can do. Try the ASp.NET forum for creating client in web matrix.

OK. The short answer is that VS 2005 Beta 2 is not a supported version for WSE 3.0. The needed steps are: Install IIS 5.0 or above Install SQL 2005 Server --I installed SQL Server 2005 Enterprise-eval 120 days Install VS Studio 2005 - I installed VS 2005 Professional - eval 60 days Install WSE 3.0 In this order. Then it wse 3.0 will install without a problem.

Thanks a lot. I am really looking for code that can be implemented in the client [in Javascript]. Much obliged. mysorian

There really was no problem. I was using Firefox browser which does not reproduce the extent of a text UI correctly and I was cutting and pasting the encoded information into my web.config file which truncated the ConnectionString. What you put in is what you get out. Moral: always double check and don't think everything will be OK.

David: There is more to it than meets the eye... ------------- PROCEDURE dbo.GetEmployeesXml AS SELECT * FROM employees FOR XML AUTO RETURN ------------------------------ Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load 'Put user code to initialize the page here If Not IsPostBack Then Dim sxcmd = New SqlXmlCommand("PROVIDER=SQLOLEDB.1;SERVER=XPHTEK;DATABASE=Northwind;INTEGRATED SECURITY=sspi;") sxcmd.RootTag = "Employees" sxcmd.CommandText = "EXEC GetEmployeesXml" Dim xrdr As System.Xml.XmlReader xrdr = sxcmd.ExecuteXmlReader() Response.Write(xrdr.HasValue) End If End Sub ---------------------------- Exception Details: System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80040E21. Source Error: Line 32: Dim xrdr As System.Xml.XmlReader Line 33: Line 34: xrdr = sxcmd.ExecuteXmlReader()--->error generted here Line 35: Response.Write(xrdr.HasValue) Line 36: While xrdr.Read ----------------------- Now I substitute the 'stored procedure' by the statement used in the procedure, voila! No exception thrown.

It is not a permissions problem.

I thank you sincerely for your efforts. The code you sent me did not work, the same message. I played around with all kinds of permissions, nothing worked. Finally I nailed down to an MSDN article.... The real reson besides the 'bug' that microsfot has found is tht the earlier versions do not support xml to the extent the 2.8 does. --------------------- There is an explanation here. I have seen in Pre-MDAC2.8 books claims that the code works, I know not how it could have? It is exasperating to deal with something that does not work. Probably it is the 'race' to produce that is responsible for this irresponsible stuff. --------------------------------- SYMPTOMS When you try to save an ADO recordset to a file that was created by another user of the system, you may receive the following error message: Run-time error '-2147286781 (80030103)': Can't save. You receive this error message if the application is in a read-only folder, even if the recordset file is in a folder that has write permissions for both users. CAUSE When you try to save the recordset to a file that already exists, the recordset object creates a temporary file in the folder of the application. This folder is a read-only folder. Therefore, the second user cannot overwrite the source file. RESOLUTION This problem is resolved in Microsoft Data Access Components (MDAC) 2.8. In MDAC 2.8, the ADODB recordset creates the temporary file in the same folder as the destination file that was used to save the recordset. To download Microsoft Data Access Components (MDAC) 2.8, visit the following Microsoft Web site: Note Microsoft recommends that you test your application with MDAC 2.8 in a test environment first, to make sure that you are aware of any compatibility issues before you decide to use (or upgrade to) the MDAC 2.8 version. STATUS Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in MDAC 2.8. By the way, the preview of this message is not working.

That would be the first thing I would try. It does return resutls in Query Analyzer. Thanks, Happy New Year Mysorian

You're welcome. We're here to help! Good luck! -- LuisR Luis Alonso Ramos Intelectix - Chihuahua, Mexico Not much here: My CP Blog!

You need to set the ActiveConnection to an ADODB.Connection object rather than to a string. The following site may help. http://www.devhood.com/Tutorials/tutorial_details.aspx?tutorial_id=640 Store your favourite bookmarks online: my-faves.co.uk

Christian: Thanks a lot. Actually, I finally made it work with ExecuteReader()method of the command. What happens actually, is that there is no streaming data and you cannot use the DataReader's Read(). There is nothing to read. However, you may just read out the Output parameter's value. I will try if the ExecuteNonQuery() works as well, as nothing is returned, but everything is contained. Thanks jay