|
| Progress Bar Control |
 |
Mon, 24 Mar 2008 18:01:06 -050 |
I am trying to learn how to use ‘Dbase’ Plus 2.61.3 by upgrading a DOS 5
program. I have a small report writing program (Plus version) consisting of a
form, Rptform.wfm, and three report writing programs, WKENDBON.PRG, WKENDCOM.PRG
, and RPTSLCOM.PRG. The form contains 3 radiobuttons (they select one of the
reports), two spinboxes (they select start/end dates) and two pushbuttons. One
of the pushbuttons is a “QUIT” button, the other STARTs one of the report
programs, selected by one of the radiobuttons, from a 3 part DO CASE and using
the selected start & end dates.
It all works fine – except – the report programs take a long time to crank &
grind with no obvious indication that anything is happening. A progress bar is
needed!
So, a progress bar was added to the form and can be controlled with statements
like:
form.PROGRESS1.value = xx
form.PROGRESS1.visible = true
but only from RPTFORM.WFM (i.e. before calling one of the *.PRG’s from the DO
CASE). I have not been able to control “value” or “visible” once I am in one of
the *.PRGs, but that is where “.value” is generated! I am reasonably sure it
has to do with the “form.this.that.etc.” in front of the “.PROGRESS1.value” -
but have not been successful finding the right combination. What have I missed?
Thanks.
|
| Post Reply
|
| Re: Progress Bar Control |
 |
Mon, 24 Mar 2008 19:15:15 -040 |
In article <Oux5wLgjIHA.700@news-server>, gei@futureone.com says...
>
> form.PROGRESS1.value = xx
> form.PROGRESS1.visible = true
> I have not been able to control =3Fvalue=3F or =3Fvisible=3F
When dBASE is busy crunching numbers, it doesn't give a very high
priority into refreshing the screen. To prevent that, have you set the
_app.AllowYieldOnMsg property to true?
Jean-Pierre Martel, editor
The dBASE Developers Bulletin
|
| Post Reply
|
|
|
|
|
|
|
|
|
|