Great article. It has definately given me some light to move forward.

I am sorry to bother you, but I am having a hard time understanding how to implement this feature in my application.

On the user site for example, when setting the folder permissions in web.config, would the classes above still allow the admin to browse the site as another user?

Do you have a a sample of an application that uses this great feature that I may be able to go through as a guide?

I understand you might be busy at the moment, but If you are available for consultation, I would appreciate it if I could take a moment of your professional time to discuss this at yor hourly rate. Please let me know asap.

I am in Toronto, Canada so I believe we are in the same Time zone.

Thank you very much in advance.

Exception:
Collection was modified; enumeration operation may not execute.

Solution:
Use for loop starting from collection end to 0 index, so you do not miss any param when it moves:

for (int i = e.Command.Parameters.Count – 1; i >= 0; i–)
if(MySqlDataSource.UpdateParameters[e.Command.Parameters[i].ParameterName] == null)
e.Command.Parameters.RemoveAt(e.Command.Parameters[i].ParameterName);

I have read many belogs, though many were usefule but what I found is:

I have used Stored Procedures to select, insert, update, and delete.

1- Visual Studio based on the parameters declared in the stored procedure creates the parameter list for any of the actions like insert
2- Based on the fields on the form VS creates the values as the parameters.

If your stored procedure has a variable as inClientID and your table field is ClientID, VS creates insertparametes as

And Binding the field on the form is

ClientID:
‘>

When iserting VS takes to parametert to pass to stored procedure

@inClientID
@Client ID

so the stored prcedure expects one parameter but receives two parameters and generates error.

The solution is :
Declare the parameter in the stored procedure as the name of the field

Like
Create Procedure insert
@client ID int
As
insert into clienttable ([clientID]) values (@clientID)
Go

In this way VS creates the insert parameter and value with the same name as clientID

To find how many parameters the page passes to a command use this code that I found in one of the belogs:

Protected Sub YourSqlDataSource_Inserting(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.SqlDataSourceCommandEventArgs) Handles HousinClientList.Inserting
For x As Integer = 0 To e.Command.Parameters.Count – 1
Trace.Write(e.Command.Parameters(x).ParameterName)
Trace.Write(e.Command.Parameters(x).Value)
Next

End Sub

Enable trace = true on your page. You will see what I am saying.

Thanks.

May God continue to grant you favor!

Keep up the great techie work. I’m gonna book mark your techie blog!