>
I don't know what "named parameters" and "positional parameters" are and how I (as a developer) have control over these. I will have to find something to read on that. >
>Dmitry,
>
>Here's another way to look at it....in SQL Server, suppose you have a stored procedure like the following...
>
>
>CREATE PROCEDURE dbo.GetOrders
>@CustomerID int, @StartDate date, @EndDate date
>as
> select * from Orders where CustomerID = @CustomerID AND OrderDate BETWEEN @StartDate AND @EndDate
>GO
>
>
>
>If I used name parameters to call the proc, I can pass in the parms in any order.....such as...
>
>
>EXEC dbo.GetOrders @StartDate = '1-1-1999', @EndDate = '1-31-1999', @CustomerID = 101
>
>
>However, if I simply pass in values without referring to the parms by name, I have to pass them in, in the original order specified in the proc
>
>
>EXEC dbo.GetOrders 101, '1-1-1999', '1-31-1999'
>
Thank you very much, Kevin. I get it now.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
