| how to stop execution in between fetching records [message #221063] |
Fri, 23 February 2007 10:08  |
amit_vass2000
Messages: 52
Registered: December 2006
Location: Delhi
|
Member |
|
|
Hello everybody,
i have creating a form in i have to fetch rows and populate them in there appropriate fields, in this i have used synchronize keyword and a display item in which counter is running. now while counter is running records are coming in there fields one by one. now i want to stop the processing by clicking on the stop button, but while records are coming all the button's attribute get false automatically.
is there anybody who can told me that how could i stop that processing in between.
thanks in advance.
|
|
|
|
| Re: how to stop execution in between fetching records [message #225380 is a reply to message #221063] |
Mon, 19 March 2007 18:48  |
 |
djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia
|
Senior Member
Account Moderator |
|
|
Forms is a block mode application. If you wish to process one record at a time then you either have to change the block properties so that each fetch returns only one row or you have to populate a non-database block manually.
If you can see the records coming back from the database then you must be either running a very slow machine or you are doing a huge amount of processing on the record when it is returned.
I dislike the concept of the code that you are trying to implement and I suggest that you spend your time on making the form work faster. That way the user won't think about having to stop the data flow.
That said, I assume that you are handling the population of the displayed fields yourself (something I also dislike) so you have to populate the non-database block via a timer initiated procedure. The timer triggered process populates a single row into the non-database block and when it gets to the last step of the procedure if the 'stop' button hasn't been pressed then the timer is recreated which in turn will start the procedure again to populate the next line.
David
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
