Vlad,

I think the idea you described should work, but I'm not sure how you would know fields needed for your report? Can you query report as table in the same time, you're running it? E.g. select expr, supexpr from reportfile into cursortemp, then analyze each expr and build a temp cursor? This extension of your idea would not work probably.

Anyway, it's not a disabling Preview feature at all, as you originally intended :) And this particular problem (disabling) doesn't seem to have a solution (not in VFP6.0, at least).

>Hi!
>
>I proposed the solution (but it was never implemented).
>Add a function call to the report somewhere that is called the first of all other things. Then prepare a temporary cursor with only one empty record. When that function called, it also runs a query. SO when user request to preview the report, the query ran to get its data. Without the preview data are not prepared for report at all. After query running just copy these data into the temporary cursor. NO run the report.
>
>Really, I never knew if above works (dynamical preparing data for report "one the fly". Though I thonk it worth to try if such feature is really needed (no data for report preview when user designing report in run-time). Just prepare these data when user requests topreview and thats all ;))
>
>
>>Vlad,
>>
>>Just curios, have you been able to figure out a solution? I guess, this is a case, which doesn't have it. These cases are very rare, but they definitely exist...
>>
>>>Hi!
>>>
>>>Good point and I completely agree with it. However, I can do nothing to this - this is customer requirement. It seems it is not such easy thing to explain them why this would be better. There are already a list of predefined queries...
>>>
>>>>Vlad,
>>>>
>>>>>>They put a textbox, then write a field name from the list of fields they have in the document. Thats all. This process do not require to have data opened, indeed, though your suggestion about preview is correct -
>>>>it is good to preview data. However, reports built that way often require complex query with tables related correctly. When user can define report layout using field names list, it is much harder for user to define the query even when we provide a smart and comfortable in use Query Builder application and interface. Because data not prepared by query (user do not know how to build it), user just buld report. Then descirbe what data exactly he want to see (which tables and filters), and another person, that specially know how to use query builder and build queries, creates the query for that report. This way only one preson will learn the query builder - complex thing, when all other will learn just a report layout making. Otherwise everyone will require to learn the query builder, that is too much...
>>>>
>>>>>>Do you see a point here?
>>>>
>>>>
>>>>I understand what you're saying, but I disagree with the content.
>>>>
>>>>Users know they want *something*, but they may not know how that thing is created, or what its composed of. When you give a user a lot of query flexibility, you need to create a dialog with that user. In terms of software interface a complex dialog may start with: "These are your options... which one do you want?"
>>>>
>>>>Word Processors such a MS Word do this with templates: "What kind of document do you want to create? Here are a set of predefined documents from which you can choose." As the user becomes more sophisticated, they typically want the capability of adding to this set of predefined options.
>>>>
>>>>It sounds like you may need to do something similar. Display a list box or grid which describes predefined queries. When the user picks a type of query, allow the user to alter the query (visually of course) or run the query and then
>>>>allow the user to modify the query after having viewed the results.
>>>>
>>>>Finally, allow the user to add the new query to the set of predefined queries.
>>>>
>>>>
>>>>Tossing a blank query system to the user is like taking a new-car buyer and putting them into a machine-shop, saying "Here, you've got unlimited access to tools and materials... Make whatever you want!" You're not going to have many repeat buyers.
>>>>
>>>>
>>>>Regards,
>>>>Thom C.