Sorry. What im saying is, if you have a datasource whom's insert command takes 3 parameters. You go in its properties, click on the little lightning bolt in the property window to access the events, find "inserting", and double click in the field. It will generate for you the Inserting stub function for that event.
Then on your button, just call Insert() and thats it, like you were doing, but without the parameters.
The Inserting event's second parameter is "e" (you'll see it when you have the stub in front of you from doing the above ).
e is an object that contains all the paramters of the Inserting event. One of which is Command, which is a standard ADO.NET SqlCommand.
One of the properties of SqlCommand is parameters, which is a simple collection of your parameters. So using the syntax that confused you, you will be able to set those parameters -right- before the Insert is done (which is what the Inserting event is). Thus by setting its values, you will be able to replicate what you were doing in your button click, but it will be done at the "right time", so to speak.
Is that easier to understand?