>------------------
>The report uses a view. Each report has a query associated with it. We
>use the one connection for entire application. If underlying table is
>changed via C++ application (through ODBC ) between two invocations of
>the report, second invocation is showing stale data.
>
>I am guessing this is a ODBC or VFP problem.
>

I do not think the problem is with the code snippet for the Crystal report. I think the problem lies with the code for adding records to the VFP tables via ODBC. Not knowing anything about C++ or how your app is doing this, I would think the problem is with commiting the transactions at the end of inserting new records.