>Not sure for NET, but when in VFP I use parameters in my queries VFP explicitly use sp_executesql to run this query.
>Just run SQL Profiler and see what command is send to SQL Server when you use parameters.

SQL Profiler always shows everything in sp_executesql mode. Does this mean this would be the optimized route to adopt? When I saw it in there, I adjusted my data class to support that approach. When I also tested that approach in SSMS, I found that it was a little bit faster. But, for now, in the data class, I have gone back to the SQLParameter object route using a native SQL command. I just wanted to make some verifications first to see what would be the best way to access the data from the SQLClient data provider in .NET.