Lynette,

I think item 1 and 2 might be due some ODBC problems. Have you checked that the Background fetching option of the ODBC driver is uncheck ? Problem 2 might be caused by this. Uncheck this option.

Have you choosen for the ODBC approach for a specific reason or are you free to choose for the FOX2X table option ? In this approach you run the queries in VFP and copy the results into a temp FOX2X table. CR can read the FOX2X tables natively far faster than with ODBC.

>Ok, here's todays final wierdness question -- VFP 6 sp5 and CR 8.5:

>3) Using Views for the data of a report, the report never updates to the revised information entered into the database. How can I FORCE CR or VFP to update the view so the data appears correctly in the report? F5 doesn't work, Validating the Database doesn't work, but the data is stored correctly in the table. How would I force VFP to update the view? (I use views because the users often have CR and VFP open and were having trouble when the report uses the tables directly) Now I don't have problems getting to the data with the view, but I have different problems with the report data being correct!

I suspect that it is looking at the views resultset wich in fact static and therefore changes in the underlying table are not reflected. I've not have much experience in accessing VFP data trough ODBC, but there has to be some way to REQUERY() the view so that the changes can be reflected (after a refresh) in CR.

Others may jump in here, as I don't have a clue how to REQUERY() a view through ODBC.

Walter,