Dave, the "Application.ProcessMessages" worked like a champ!

Thanks loads!

--- In [email protected], David Smith <djsmith_1...@...> wrote:
>
> Find a few convenient places in your code to make a call to 
> Application.ProcessMessages. Also, make the cursor go to a SQLWait cursor so 
> they know that your program is still processing. You could also provide a 
> gauge in the status bar indicating how much processing is remaining.
> 
> Dave
> 
> --- On Sat, 2/27/10, c80840 <c80...@...> wrote:
> 
> From: c80840 <c80...@...>
> Subject: [delphi-en] Refreshing
> To: [email protected]
> Date: Saturday, February 27, 2010, 6:04 PM
> 
> 
> 
> 
> 
> 
> 
>  
> 
> 
> 
>   
> 
> 
>     
>       
>       
>       I use BDS2006, and I hope someone can give me advise.  My program is 
> set to having a main form, then using MODAL, I open another form where I 
> process a database.  While processing through a database, if I go to say for 
> instance MS Word, and go back to my program that is still processing the 
> database, the program screen won't refresh until the program completes 
> processing the DB.  
> 
> 
> 
> So if it is a real big DB, the user might think the program has hung, and 
> force a termination through the Task Manager, when it really isn't necessary. 
>  I have tried to refresh the form after each record is processed, but that 
> didn't help.
> 
> 
> 
> Can any your brilliant folks here tell me how to fix this issue?  I want to 
> be able to allow the user to go to another program, and come back and they 
> can see things working.  On the bottom of the screen, while it is processing, 
> the status bar displays the record number that it is on.
> 
> 
> 
> Thanks...
> 
> 
> 
> 
> 
>     
>      
> 
>     
>     
> 
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
>       
> 
> [Non-text portions of this message have been removed]
>


Reply via email to