Hi Kevin,

Thanks for the input. I finally found the problem and it seems to be a VFP problem. My numeric field is N(7,2) but some values greater than 9999.99 were stored as N(8,1) (my mistake to have these values in a N(7,2) field but why did VFP took them anyway...) and this made the VfpOleDb provider fail.

Kind regards,

Thierry

>Thierry,
>
>>I am playing with MM.Net and using it to access my VFP data for a Web application.
>>
>>My GetSomeStudents() method works well with the following SQL statement:
>>
>>SELECT stu_clast, stu_cfirst WHERE UPPER(stu_clast) LIKE 'L%'
>>
>>but it fails with:
>>
>>SELECT stu_clast, stu_cfirst, stu_npnts WHERE UPPER(stu_clast) LIKE '%L'
>>
>>I get an error message saying "The provider could not determine the Decimal value. For example, the row was just created, the default for the Decimal column was not available, and the consumer had not yet set a new Decimal value." (see full message at the end). stu_npnts is a numeric field N(7,2). This query works fine in VFP but fails with .Net
>>
>>My questions are:
>>#1 Any idea why this fails?
>
>I haven't personally seen this error before, but I found this information from someone who experienced the same problem:
>
>http://64.233.161.104/search?q=cache:IrYyQKB7CTQJ:dbforums.com/arch/213/2003/7/841025+%22the+provider+could+not+determine+the+decimal+value%22&hl=en
>
>Regards,