It's a really, really bad idea. SQL Server will generate a query plan for the first set of parameters, cache it, and reuse it for all future calls to that stored procedure regardless of how the parameters change. Stored procedures work best when the shape of the query - the tables involved, how they're joined, the columns filtered by the WHERE clause, and the order of the output - remains stable. They don't work if you try to change the shape of the query. SQL Server accepts parameterized SQL text - with @variables in the command text - and it caches the query plans for parameterized queries. It also tries to automatically deduce where parameters should be if no parameters were used - this is referred to as auto-parameterization. It still caches the query plan even if it can't deduce the parameters. However, it ranks the cached query plans so that a plan for a stored procedure is likely to be kept longer than a parameterized query, which is likely to be kept longer than an auto-parameterized query, which in turn is likely to be kept longer than a non-parameterized query. Unless you really want to prevent users from SELECTing from the base tables - using the security barrier you can erect using stored procedures - I strongly recommend using parameterized, dynamically-constructed queries submitted as text. DoEvents: Generating unexpected recursion since 1991

The SQL Server OLE DB provider and ODBC driver, plus associated network libraries, are part of MDAC (Microsoft Data Access Components) for SQL Server 2000 and earlier. At least MDAC 2.6 is required for accessing SQL Server 2000. Since Windows 2000, MDAC is part of the operating system. Windows 2000 shipped version 2.5 so requires updating to access SQL Server 2000. Windows XP SP2 ships the latest redistributable version 2.8 SP1. Windows Server 2003 SP1 ships with MDAC 2.8 SP2 which is not available separately. Basically, on Windows XP or later you don't need to install extra software to access SQL Server 2000 or earlier. The .NET Framework implements the SQL Server access protocol natively, but requires the network libraries from MDAC. You can access SQL Server 2005 using the SQLOLEDB provider for ADO/OLE DB, SqlConnection from .NET 1.1, and the SQL Server ODBC driver. However, the old provider does not support many new features of SQL Server 2005. To get full functionality, you need to install and use SQL Native Client (for ADO/OLE DB/ODBC), or use .NET Framework 2.0 or later. For ADO/OLE DB, specify SQLNCLI rather than SQLOLEDB. For ODBC, use the 'SQL Native Client' driver rather than the 'SQL Server' driver. Stability. What an interesting concept. -- Chris Maunder

i didn't get u still the same prob iam getting plz help

hello sir thanks 4 the reply but iam not asking abt dumping the same asp pages to .net asking about ingeneral how the .net projects are implemented in 3d

You're in a .NET board. Repost your question to a board that deals with ASP if you expect an answer. "Some people spend an entire lifetime wondering if they made a difference. The Marines don't have that problem." ( President Ronald Reagan)

hello sir thank u very much it helps a lot to update thanks once again

Hi, I think you must use ASP.NET User Controls (*.ascx)

If you just want to use that function in multiple pages then what you can so is place that function in a class file and then call it from the pages where ever you want. Best Regards, Apurva Kaushal

You can use asp:imagebutton.

In design view right click on the datagrid and select edit template. Or just write out the HTML. how vital enterprise application are for proactive organizations leveraging collective synergy to think outside the box and formulate their key objectives into a win-win game plan with a quality-driven approach that focuses on empowering key players to drive-up their core competencies and increase expectations with an all-around initiative to drive up the bottom-line. But of course, that's all a "high level" overview of things --thedailywtf 3/21/06

disassemble it. google is your friend here :) regs, g00fy