>>>>>
>>>>>Given your previous post I guess you no longer need it but, in pseudo-code:

SqlCommand command = new SqlCommand();
>>>>>            //Congfigure command
>>>>>            SqlParameter param = new SqlParameter(Parameters[2, 0], Parameters[2, 1]);
>>>>>            param.Direction = ParameterDirection.InputOutput;
>>>>>            //etc
>>>>>            command.Parameters.Add(param);
>>>>>            //Add other params , execute....
>>>>>            var v =  command.Parameters["@Param3"].Value;

>>>>
>>>>Can you think of why when I am trying to apply the above code, C# compiler complaints that 'object does not contain a definition for 'Value'". This is on the very last line where Parameters value is retrieved. And when I entry the open bracket key, right after the 'Parameters' Intellisense shows that object List parameter is int Index. What am I missing?
>>>
>>>Can you show the code you're trying?
>>
>>I think the difference is in how I create Parameters collection (as following):
>>
>>

>>IDbDataParameter param = oCommand.CreateParameter();
>>

>>
>>and the way Viv created them:
>>
>>

>>SqlParameter param = new SqlParameter(Parameters[2, 0], Parameters[2, 1]);
>>

>
>Yes, that's the difference. I think you need to have two separate classes - one for calling VFP SPs and one for SQL Server to utilize SQL Server specific provider and not generic.

I will try this approach. Thank you.