PAGE UP/PAGE DOWN HANGS EXE

[harryjr]

Have converted a FPW 2.6a Application to VFP (i.e., compiled not rewrote).
Application contains multi screens - each with multi gets controlled by a READ CYCLE MODAL. In VFP 5.0, Applications HANGS UP when attempting to CYCLE thru the Screens using PAGE UP/PAGE DOWN keys. MSKB acknowledges problem and instructs to REPLACE "PAGE DOWN" with "TAB" - "PAGE UP" with "SHIFT TAB".
Page UP (SHIFT TAB) works OK. Page DOWN (TAB) does not.

Any ideas????

TIA

Harry Riley

 

[JDurbin]

I dont know what it does but you may just put code in the lost focus or valid of the last control to go to the next form. Are forms hidden that aren't activated? Can you click between forms? I'm sure you know how rewrites are the only real way to convert so I won't preach. If the second form's first control goes to the last control on the first form ok with shift-tab, I'd snoop to see what code the convertor put in the valid or lostfocus methods. How does it know to switch forms? I'd apply the logic going the other way. Why the conversion works one way and not the other I dont know. Someone else may have more experience with it. Or you may want to post more info with method code. HTH John Durbin

http://www.EPS-Software.com

MCP Visual FoxPro
ICQ VFP ActiveList #73897253

 

[holzert]

Did you try using:

#IF 'WINDOWS' $ UPPER(VERSION())
ON KEY LABEL PGUP CLEAR READ
ON KEY LABEL PGDN CLEAR READ
#ENDIF

And then you will have to activate the next page of course. We trap for inkey() or lastkey() in 2.6 screens running in VFP6. During the conversion of 2.6 to VFP6, we brought the 2.6 code in to VFP6, copied the original 2.6 .sprs into the project after the project conversion was done, and then ran the original .sprs in the app, not the converted the screens.