Kevin,

>Again, thanks to both of you. I'm making good progress!<

You're welcome! Glad to be able to help.

>Having said thatm, if my choice of data types is not the best, or my
>procedure could be tweeked, please advise.<

I'd avoid the Unicode datatypes (nchar, nvarchar, etc) unless you have a reason to use them. You should use char, varchar, etc. instead. The Unicode data types take up more space. See SQL Server's BOL for more info as to when you might need to use the Unicode types. Search for "Unicode data type".

~~Bonnie



>Worked perfect!
>
>As I said in another post, I am learning .Net. Up to now, I have
>been a hard core VFP type, and aside from pulling some simple SQL
>data here & there, I have never really worked with SQL.
>
>Having said thatm, if my choice of data types is not the best, or my
>procedure could be tweeked, please advise.
>
>Again, thanks to both of you. I'm making good progress!
>
>
>
>
>>ok....I don't work with nChar much, but I would have thought you'd need to specify a length in your parameter.
>>
>>I modified one of my simple SPs to receive the parameter as an nChar...if I didn't specify a width in the parameter list at the top of the SP, (e.g. nChar(10), it didn't work, but the minute I specified a width, it worked fine.
>>
>>I don't know if that's the full answer, but give that a try.
>>
>>Kevin