You can activate internal query progress bar

	
* Save SET TALK and SET NOTIFY settings
...
DEFINE WINDOW talkwind FROM 12,30 TO 16,70;
	SHADOW COLOR SCHEME 5 DOUBLE NAME loWind
ACTI WINDOW talkwind NOSHOW
SET TALK WINDOW talkwind
SET TALK ON
SET NOTIFY ON

* Run QUery
SELECT ...

* restore SET TALK and SET NOTIFY settings
...
* release window
RELEASE WINDOW talkwind 

>I am running into a slight problem. I have a section of code that uses an SQL statement which is somewhat CPU intensive. Unfortunatly, there are some end-users that use this application that I have found are very impatient and even though I display a wait message, they still think the program locked up and "Alt+Ctrl+Del" out of the application. This is a problem because doing so when a table is being access has sometimes corrupted the table. I was hoping to be able to display a dynamic message using the WAIT command that scrolled a "." at the end of the message based on a timer. This way at least the message would show some "activity" and the user would not immediatly think that the application "froze". I tried adding a timer control, which I activated immediately before the SQL statement, but it appears that the SQL Statement halts all code from processing, even the timer control. Does anyone have any idea what I could do to get this idea to work?
>
>This is the code I use inside my timer: (Note: Timer Interval = 500)
<snip>