OI Ver 7.2.1
From about a year ago… I still have problems hearing an annoying beep sound (windows default beep) for every OIPI page break. I have tested this on three seperate computers and got the same results.
I just can not have a customer printing 200+ delivery documents daily, and having their computer beep 200+ times. I also can not imaging me doing a demo at a customer site and telling the customer… oh that noise is normal.
Can someone verify this please? Or has this been resolved?
Be sure that your system does have a sound assigned to the "default beep". Control panel ] Sounds ] Sounds tab ] Sounds Event ] Default beep.
I have default beep defined. Never get this behavior (ie, no beeps while report is being created in preview). tried w/ 14 pg rlist rpt and 10 pg rbasic created rpt. tried sending rpt straight to a CSV file - still no beeps (although I managed to get one by canceling after selecting records)
However, did notice that if you click to change focus to main menu of OI app from print preview, it beeps (once). just changing focus anywhere else doesn't seem to cause it to beep. could your code be causing a reset of focus or a click event on the app's menu?
Thank you Karen.
I have narrowed it down to the "SET_PRINTER('INIT', " sentence. I will look further and test some variations to the SET_PRINTER parameters so as to try to eliminate it or isolate it better.
I have noticed the same in my un-attended daily reports. They do not annoy anyone since the reports are coming from a Terminal server but I am interested to find a reason for it since I can hear them when I run the tests during program development.
I placed test statement 'Call MY_REPORT' as the last statement into my login form's create event, just before Return 0 and I hear the bell after every page.
When I added a test button to my login form with only statement 'Call MY_REPORT' and clicked that w/o logging in I did not get the bell???
Very mysterious. I have been unable to figure out what is causing it but I doubt it is Set_Printer (INIT.. . Please let us know if you have better luck finding this out.
Richard,
OIPI is looking at @WINDOW. If there isn't @WINDOW the beep will occur.
Sean
Are you calling any message boxes or updating status lines while the report runs?
I managed to find a few reports that beep once (when first started) – all are displaying a msg box on startup (the same report if called in another way suppresses the msg box and does not beep).
How do I set @Window?
E.g. @Window=LOGIN' doesn't seem to do it.
I don't think you can set @window? It is set by the fact that you have an open window…
The only way I know how to run these un-attended reports is to call them from forms CREATE Event. Even If I have another form already open doesn't seem to help??
Any other way to automatically run e.g. 'Call MY_REPORTS" after the CREATE event has completed?
I use a job processor. This is basically a program that scans a queue for job/reports and processes them when it is time. It is "started" by clicking start on a window.
My @WINDOW variable is not null.
I have an open window. This window is calling a subroutine during a POST_EVENT process. This called subroutine is doing all the SET_PRINTER sentences. This called subroutine then returns within the POST_EVENT process that then does a POST_EVENT(@WINDOW,'CLOSE').
I did comment out the POST_EVENT(@WINDOW,'CLOSE') sentence. The window was still open during all SET_PRINTER sentences. And the window stayed open even after I closed the OIPI preview window. I still heard the beeps!
Thanks but no can do.
It's run automatically on a server in another country in a locked vault of a computer center with scheduler using e.g.:
C:\REVSOFT\OINSIGHT\OINSIGHT.exe /AP=MYAPP /HE=1 /UN=DAILY /PW=XXXX
so there is nobody clicking any buttons to activate it.
I think John is saying that he runs a scheduler within OI, rather than using the OS scheduler. I do the same with my own scheduler (OS schedulers do not offer the features I want). My MDI frame includes a TIMER event which calls my OI scheduler routine every minute to scan for jobs, replacing the "click" John refers to. Since the MDI frame is open to @WINDOW, no beeps.
Is it a problem for OI to run continuously in that locked foreign security vault? If not, having OI run the scheduler with a TIMER event should resolve your question.
We are kind of short with our license count so I do not want run it continuously and consume one license with it.
The beep is not a problem but just wanted to get to bottom of it and remove it if possible.
Running the reports (DAILY, WEEKLY, MONTHLY, YEARLY etc. 50+ of them) from CREATE event works fine but I was hoping there would be other solution for it.
Since it only occurs if you have a default beep sound assigned, why not just remove it? Doesn't sound like it is needed (on your demo system or when locked in a vault).