I killed off the view the other day from the form, but it was still in the Report's DE. I had so many problems trying to get the view to update a NEW record, but it would not do the update, although everything looked good with the TableUpdate function. A simple change to the data was easily updated, but it would not update an APPEND. Anyway, I killed that view and went back to related tables in my form. I forgot that the Report had saved the DE. When I hacked into the REPORT FORM's table, I found three records still holding cursor info, so I deleted all three records. Luckily, I did no harm and the REPORT FORM opened up just fine. If I had kept the Local View, I'd have used REQUERY, as I had already put it into the Activate event to pick up the newly selected Customer info after leaving the Customer form. I wrote a simple SQL SELECT and saved the resulting data into a temporary cursor for the report form to use.

All in all, I dropped the View and things have been much easier. I deleted three records in the REPORT FORM itself, and everything is running nicely once again.

Cecil

>Have the report query the data for only what it needs. Use a View Parameter to make it easy. Then just REQUERY() the view.

>>I had my SET VIEW ON operational and saw an old LV_ORDERS view open, which means that the REPORT's DataEnvironment is still holding that view. This is why it won't work. I am going to have to see how to clear out the old DataEnvironment.