>Vlad-
>
>>Is it possible to prevent at all previewing of the report during designing? When putting return .F. in the Init and BeforeOpenTable in data environment of the report, this works only in design time. When standalone VFP EXE run, this does not works.
>
>I agree with Hilmar. It would be very hard to design a report if I couldn't preview it.
>
>If it's a problem with data security, or data access, could you let the user use a sample data set?
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.
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.