>P.S. CR 9 works find VFP 8 if you use ODBC and don't try and use the autoinc data type.

We've had a couple problems with CR9 and VFP8 (don't know about CR9/VFP7):

1. CR9 keeps data files open even after the RDC and Report objects are set to NULL. This can be reproduce via OLE DB, ODBC, VFP8, VB .NET, ACCESS. In my applications, I use temp tables for reports (I delete and recreate these tables between printouts). With CR9, it keeps the data files open and I cannot delete them unless I close out of the application - CR says this is by design, but I'm fighting it all the way to the top. In CR v7, we had to open a different report to release the data files from the previous report. In CR v8 and v8.5, the data files closed with the report (which is the way it should be!). In CR9, nothing will close the data files and I'm having to rewrite my logic to work with the tables that cannot be deleted after they've been used by a report. AARRRGGG!!!!!!

2. We just resolved an issue this afternoon with CR9/VFP8 that had to do with the June developer monthly hotfix that was applied in an attempt to fix item #1 above. The fix to this problem was to apply the most current main application monthly hotfix since there can be problems when one hotfix is applied without the other in VFP8 (but the readme doesn't say anything about this cross-hotfix dependency). This problem did not rear it's head in VB.NET.

Anyway, seems like it's always a chore dealing with a new version of CR in VFP. If an updated VFP OLE DB Provider will make my life easier, let's have it!

Regards,
Bill




>William,
>
>The problem with Vfpoledb is it can not enumerate a large number of stored procedures. A couple of weeks ago Ken Levy indicated an updated driver was only a week or so away. Haven't been on UT to check it out. Not sure if/where it is available.
>
>Can anyone else help here?
>
>Jeff
>
>P.S. CR 9 works find VFP 8 if you use ODBC and don't try and use the autoinc data type.