Did want this to get lost, so I am reposting.

Not to be picky but I think I found another issue with OIPI32.

If you are previewing a large report and press the Exit button instead of cancel the report continues to run without the viewer.

Also, the cancel button cancels the report but shows a blank viewer. It used to show the report up to that point in OI16.

I can imagine customers doing this and thinking their machine is locked and restarting…

Thanks,

John

John,

Is this occurring on a specific OS?

Sean

Sean,

Thanks for your reply. I tried this on NT 4.0 SP6a and XP Pro and had exactly the same symptoms.

HTH,

John Bouley

John,

Are you writing your own OIPI reports or are you using S/List? If the former, are you error trapping?

Can you give me an idea of what a large report is to you? Also, are you saying that smaller reports exit normally? I'm wondering if the problem actually exists all the time but smaller reports complete their task so quickly that it goes unnoticed.

We can try to duplicate on our end as we have some large reports as well.

[email protected]

SRP Computer Solutions, Inc.

Don,

I am using Slist.

Small reports have the same problem but they complete in a short time and it is not noticed.

If a report (more than one page) is taking a long time I often do not want to wait for it to finish and will press cancel. The cancel button does stop the report but shows a blank viewer. If I press the close button the viewer disappears but the report continues to generate and control is not returned to the calling program until the report actually finishes.

Here is some sample code we are using to generate reports.

…

scr=Msg(WindowName,"Processing. Please Wait…":@FM:"U")

Call Rlist_Rpts(WindowName,RpRec,Dest)

x=Msg(WindowName,Scr)

If Dest=T" Then

• Set Focus to Preview

 Hwnd=FindWindow("ThunderRT6FormDC":\00\,0)

 If Hwnd  0 Then Call SetForegroundWindow(Hwnd)

End

…

Rlist_Rpts builds the select statement and places either "SCREEN" or "PRINTER" onto the statement. It then calls Slist(Sent).

Anyway, this used to work on OI 3.7.5 but not in OI 4.1.1.

HTH,

John Bouley

John

We are aware of these issues as they impact S/List and have been talking to RevSoft about them. But you are correct these issues do exist.

The Sprezzatura Group

World Leaders in all things RevSoft

Is this an issue with OIPI or SList?

On a side question, when using Slist I have a query that selects from LEADS_DETAIL but a report that prints from LEADS. Each table has the same key structure. I attached the query to the report but am receiving an error message "PRIMARY_SALES_REP is not a valid select column name in LEADS". The query does work by itself and there is a columnh called "PRIMARY_SALES_REP" in LEADS_DETAIL.

Thanks for your help,

John

Yeah, that would make sense because the parser takes the query and appends it to the list for the select.

So, if your query is

SELECT FILE1 WITH A=1 AND B=2

and your list maps out to

LIST FILE2 A B

this would be like entering

LIST FILE2 A B WITH A=1 AND B=2

This makes for an nice enhancement, an 'execute query independant' flag. We'll add it in to the next major release.

The Sprezzatura Group

World Leaders in all Things RevSoft

View this thread on the Works forum...