Thierry-

>#1 Thanks for the input. I found the problem and it is a VFP issue. My field was N(7,2) but some values were nevertheless greater than 9999.99 and were stored as N(8,1). This made the VfpOleDb net provider fail.

Cool.

>#2 According to Dino Esposito only the OLEDB adapters for the Jet engine, SQL Server 6.5 and Oracle 7 are garanteed to work well with .net. I remember also reading the word "certified" somewhere else in some doc but can't recall where.

Guaranteed is an awfully strong word, and you don't mention a cite so I have no idea what context his comment was made in. I don't know if Dino even has any exposure to the VFP OLEDB provider. Not to say there aren't sound reasons to use a different backend (and therefore OLEDB provider). For example, the SQL provider is optimized for .NET and so should be really great.

All that said...I appreciate the efforts MS has put into the VFP OLEDB provider in the recent past. The initial releases weren't so hot, but they were a start. So, anyway, I'm just giving you my experience, which has been good. If it's a choice of not doing a web front end or using the OLEDB provider, I'd encourage people look at the option seriously.