There are several threads dealing with issues of both the VFP7 VFPOLEDB provider and the one in release candidate for VFP8. The problem has to do with enumerating stored procedures under various circumstances. It does not appear for simple databases, but appears with certain RI configurations and certain stored procedure configurations. It is reproducible using a simple test tool, as described in one of the threads.

The problem does not show up in CR8.5, but appears with CR9. CR apparently started enumerating stored procedures with that version. The problem is not CR's, but is in VFPOLEDB.

Jeff Southworth confirmed and expanded on my observations.

Search on VFPOLEDB for details.

Unless MS released an updated version of VFPOLEDB for VFP7 that I don't know about, the problem is still there. I don't yet have the final release of VFP8 to test against.

...Jim


>I don't know why you think that? I've used both the VFP7 and 8 OLE DB providers just fine.
>
>
>>Except that CR 9 does not work with VFP7 ADO. Nor with the final beta of VFP8 ADO. I haven't tested it with the RTM version of VFP8 ADO.
>>
>>...Jim
>>