>>I'm getting this error from a vb.net access via oledb
>>
>>"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."
>>
>>It happens when you allow VFP to store an n(6.1) amount in an n(6.2) specified field. For example 1 000.5 will fit in a n(6,2) field. But when you try to retrieve that via oledb you get the above error message. The workaround is a) redefine the field as n(7,2) of course, or b) get the field as a string in the SQL.
>>
>>I was wondering if there was an even smarter way to trap this.
>>
>>Thanks for caring and kind regards,
>>
>>Marc
>
>
>Just don't allow such things to happen.

And a good way to do this is to specify the structure on the target, i.e. roll your own fields, as in the schema related properties of the cursoradapter. Specially if you control the source, and IIRC Marc may be importing data from third party tables.