|
Home > Archive > dBASE Questions and Answers > July 2005 > dBase "browse" command
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
dBase "browse" command
|
|
| Tony Speekenbrink 2005-07-05, 7:23 am |
| iI have many programs that I wrote for Visual dBase 5.7 that incoprporate a "BROWSE" command to review or edit information before resuming program execution. In dBase 2.5 "BROWSE" does not pause the program, and I did not manage to devise a work-around du
ring my "trial" period. My investment in Visual dBase 5.7 programs is such that I can't consider upgrading to a current dBase version without such a work-around. Suggestions please?
| |
| Ronnie MacGregor 2005-07-05, 7:23 am |
| In article <H5dQKIUgFHA.1756@news-server>, speekb@clinmed.gla.ac.uk
says...
> I have many programs that I wrote for Visual dBase 5.7 that incoprporate a "BROWSE" command
> to review or edit information before resuming program execution. In dBase 2.5 "BROWSE" does
> not pause the program, and I did not manage to devise a work-around during my "trial" period.
> My investment in Visual dBase 5.7 programs is such that I can't consider upgrading to a current
> dBase version without such a work-around. Suggestions please?
Hi Tony
DOS programming is procedural, and your code will run from beginning to
end unless you introduce a pause in some way. In Windows programming the
user is free to jump around as they wish, each user input event can
trigger a chunk of code to run which deals specifically with that event.
You could argue that a Windows program spends most of it's time
"paused", waiting for user input.
All you need to do is decide how the user should confirm that they have
finished "reviewing or editing" to trigger the next chunk of event code.
A simple "Next Step" type pushbutton would do the job.
--
Ronnie MacGregor
Scotland
| |
| Robert Bravery 2005-07-05, 9:23 am |
| HI,
What about creating a generic form with a grid on it. A default query and
database class. The when the form is called initiate the data and query
class, and datalink the grid.
Robert
"Ronnie MacGregor" <no@spam.thanks> wrote in message
news:MPG. 1d34722ec2895bf59896
94@news.dbase.com...
> In article <H5dQKIUgFHA.1756@news-server>, speekb@clinmed.gla.ac.uk
> says...
>
a "BROWSE" command[color=darkre
d]
dBase 2.5 "BROWSE" does[color=darkred]
during my "trial" period.[color=darkred]
upgrading to a current[color=darkre
d]
>
> Hi Tony
>
> DOS programming is procedural, and your code will run from beginning to
> end unless you introduce a pause in some way. In Windows programming the
> user is free to jump around as they wish, each user input event can
> trigger a chunk of code to run which deals specifically with that event.
>
> You could argue that a Windows program spends most of it's time
> "paused", waiting for user input.
>
> All you need to do is decide how the user should confirm that they have
> finished "reviewing or editing" to trigger the next chunk of event code.
> A simple "Next Step" type pushbutton would do the job.
>
> --
> Ronnie MacGregor
> Scotland
|
|
|
|
|