Hi Lutz,

It seems I need more timne to understand what you say. I will come back on Wednesday.

Gerhard


>Hi Gerhard,
>
>The reasons for the different results are obvious
>
>The view in the private DE opens up all tables, and cascading views from scratch, so you get the most recent data
>Also view parameters must be set to the right value. You can not just open the top view of a cascade ....
>
>In the non private DE the view uses tables and views that might be open for ages and hold data of the same age.
>A view uses data from an ALIAS rather then from a table. A Cursor named like some table will be used if existing ...
>
>
>Your approach will will mix up the result of the report with the data on screen.
>I, like others here, would not recomend this. A refresh of the data (REQUERY() ) might help.
>IOW. Look what gives differnet results and why, and change it, so that the data that you pull the data from will be up to date / mark it as data from old snapshot if needed.
>
>If you realy need to set it to private Report DE's OPENTABLES should be the right place to do all the SET commands you do usually in a form with a private DE. Note that this need to be all the private SETs DELETED might not be enough Sysformates ... DATE,,, and so on. I have a class doing this which I can snap in.
>
>HTH
>
>Lutz
>
>>Hi Tore,
>>
>>I did not mean to offend you with my answer. I am sorry and apologize if I did.
>>
>>I use views in reports for years now. And I have a report with a view in the DE, that gives dramatically different results, if Private Datasession is marked. Therefor I need to know, how I can change the settings for a private datasession. The INI of the DE is not the solution here, because I need to change the settings in an EXE.
>>
>>Any idea how to change the settings in the EXE?
>>
>>TIA
>>Gerhard
>>
>>>Well, you want to do it the wrong way, so I suggest that you do it the right way. Running reports from live data can give very strange results, since the data may change while the report runs. Especially if the reports takes a long time to run, changing data may really give you headaches. Running the reports from cursors means that you will run them from a snapshot of the data as it was when you started the report routine.
>>>
>>>If you really want to shoot yourself in the foot, I can of course help you loading your gun. But I would rather give you a warning first.
>>>
>>>>Thank you Tore!
>>>>
>>>>Do you have an answer to my question?
>>>>
>>>>
>>>>>>Happy New Year!
>>>>>>
>>>>>>I want to set some values like SET DELTED OFF for a Private Data Session of a report.
>>>>>>
>>>>>>Where can I do this?
>>>>>>
>>>>>>TIA
>>>>>>Gerhard
>>>>>
>>>>>I suggest that you always run your reports from cursors, not directly from the tables.