>It didn´t work for me. But thanks anyway.

Does the report contain any OLE Objects or pictures? Those can take a while to load, too. Same if you have functions in the report and a non-connected network share in the path.

The easiest way to find out what actually is causing the delay is to run Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) while you open the report. Process Monitor displays all file activity, letting you see if VFP tries to connect to a non-existing location, or reads so much data causing the delay.