This is kinda cool...

When I checked it with a browse statement, I got an error reporting that "field assigned_to not found" When I ignored it, there was no error on the report form command, but the report form command didn't generate a report again.

I checked and I set the active table just before my "do form" command in the main program.

I changed the click event so that it explicitly selected the table I needed before the command, and tada, it worked.

That will teach me to be lazy, I guess. Anyone have any idea why my selected alias got changed? Is it because with two forms, I ended up with two data sessions or something?

>That was my first thought too, however, the exact same report criteria are used when the report is run either way... I'll replace the report form command with a browse command just to be sure, but I don't think that we have hit upon the solution yet!
>
>>>The problem is that when I generate a "report form ... preview" from a form called from another form the preview window immediately disappears. If I call the report without using the first form, then the preview window sticks.
>>>
>>>ie, form UTIL_PROG calls form TORTOISE which issues a REPORT FORM ... PREVIEW which flashes on the screen and then goes away. Its kinda like having a form without a read events in a .exe.
>>>
>>>I suspect its a modal or windowstate problem, but since I still haven't gotten a handle on what modal means, I can't fix it without just going thru all the possible options.
>>>
>>>Please advise the best way to handle this? Thanks! :-)
>>
>>I has happened to me when an empty cursor or table is selected when the Report F
>>Form command is issued.
>>
>>
>>Oscar