>>I realized that when I print a report trough the CR OCX, the datafiles (native DBFs) used in the report (not the ODBC data), remain owned by the application after report finishes, until I close VFP (not just the form). You can see this fact if you try to change the name or delete the file while the application is up.
>>With ODBC data, the files are released inmediately when the printing finishes or you close the preview window.
>>I need to delete the files after printing as they are temporary files and the VFP application must continue running. I can't use odbc for this files, as they are independent and can't be linked to the other databases I use trough ODBC.
>>I'm using VFP 5.0a and CRW 6.
>>Could someone give me any help?
>
>I had the same problem. The way I got around it was to remove the Crystal OCX after each report and re-create it before the next one.

Elyse,

The Crystal OCX is in a form that I execute with do form and releases when the report is printed or the preview window closed. Even when the report finishes and I release the form (and the OCX in it I supose) the files are owned by the application until the main VFP application closes. In the other hand, remove and re-create the OCX it's really and dramatic slow.
I'm not sure if this is a problem of Crystal or of the driver ODBC.
I realized that a lot of temporary files (DBFs) that Crystal Reports itself creates, are deleted when the form that contains the CR OCX is released (not when the preview window is closed).