Sergey,

Thanks for your reply, I see that I'll have to take a road I didn't want to.

What doesn't make any sense to me are two things: 1) go through 80 systems to update/register the driver and 2) if the vfp oleb driver is a software to use from non-vfp apps, why not to include its latest version in the separate install rather than in the SP (if it was a choice)?.
Specially when there are issues (could be bugs, I don't know) in the oldest version.
Talking about things contributing to the "VFP + .NET integration"....