Vlad-

>Well, originally it worked that way. However, there might be very long query for report, as well as user can design report not knowing what fields really needed for it or not having data handy. Process flow in such case: Create report layout, design report, then, later, create query and run it, then test query if it returns correct result for report. When designing report, it is not possible to know what fields are required to create temporary empty cursor for it. When using it even without records, report preview show errors for fields that does not exists in the temporary cursor. When using no cursor, preview cause Open dialog box, that also not a good thing. This is a main reason why preview should be disabled.

Er. I'm afraid I'm having a hard time following this. The reason the user doesn't have the data available to preview a report is because the query hasn't been created yet? Guess I'm still really unclear on how someone is picking fields and arranging them on a layout without knowing what they are.

One of the projects I work on...my boss has an "Example" data set that's a copy with a small set of records. It was my idea that you could something similiar, but that only works if you can include the query in the dataset.

IAC, I doubt there's any way to remove the preview. However, if they've laid in a field without an alias...just the field name, and there is no data open in the report's datasession, preview won't actually do anything. It just closes immediately.