I forgot about the problem with the grid having focus. Thanks Nadya!
Tracy

>There is one nasty problem with reports. If there is a grid on the form, which has focus in the time the report is running, it switches alias to its own. E.g. If Grid's recorsource is Alias 1 and Report needs to use Alias2, sometimes Alias1 is chosen.
>
>The solution is: either separate report's DS from form's DS or make sure, that focus is not on the grid.
>
>
>>Why not run the report in a private datasession? That usually prevents these types of problems. However, have you tried opening the datasession window from inside the menu just before you run the report (in the problem cases) and viewing the datasessions to see what datasession you need and what datasessions are active when the report is run? I believe that if you have a form opened with a private datasession and you run a report from a menu that the report will try to use the form's private datasession by default.
>>
>>Tracy
>>
>>>By any chance is the report running in a private datasession?
>>>No, it is not.
>>>
>>>
>>>Additionally, make sure that the last line before issuing 'report form ...' is a SELECT statement for the main table the report uses. Then set it back after you run the report.
>>>
>>>Yes, the last line before "report form.." is the SELECT statament.
>>>The extrange situation is that it works perfectly from the button.

.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"