>Trust me, I would love too! However, I'm contracted to fix the problem not rewrite the program. The client doesn't want to spend the time or money to bring the code up to today's standards. It's been very hard for me to find all these earlier fox commands but I thought someone out here might know. Thanks for your responses though...
OK, I can understand that. Unfortunately, then, I know too little of the old-fashioned syntax to be of any real help in this particular case.
Or perhaps I do remember a little, after all. Let's see...
Perhaps you can have a push-button as part of the @...GET, that will activate the next screen.
Or if you prefer PageDown, just define the READ as non-circular. Define a number of GET objects, and a READ. When the user gets out of that (with PageDown), the next page of commands appears.
Like this:
@ ... GET
@ ... GET
@ ... GET
READ
@ ... GET
@ ... GET
@ ... GET
READ
Regards, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
