Listbox: FPW26 code running under VFP9 won't refresh

[andrewlee]

Hi all, especially Craig Boyd & Mike Lewis,
I posted this a couple of days ago and was advised of your replies but the post, along with your replies seems to have been mysteriously deleted.I've advised Tek Tips Support about this.
To re-iterate, a screen coded in FPW26 with 2 listboxes ran fine under VFP6 and VFP8. The 2nd listbox does not refresh running under VFP9. Code in the When clause of the 1st listbox uses SHOW GET to refresh the 2nd. The only way to get it refreshed under VFP9 is to click in it.
Can I ask you kind gentlemen to re-submit your replies ?
Thank you
Andrew

 

[andrewlee]

Oops-I forgot to mention that that the above behaviour occurs only with cursor driven listboxes. Array driven listboxes refresh properly.
Cheers
Andrew

 

[craigsboyd]

>>SHOW GET to refresh the 2nd

Use something like Thisform.Listbox2.refresh() and you will probably have better luck.

SHOW GET is the old way of doing things.

SweetPotato Software Website
My Blog

 

[andrewlee]

Craig,
I'm actually running code that was written in FPW2.6 i.e. the .spr file that was created with the FPW2.6 screen generator. I launch it in VFP9 with code like DO MYFORM.SPR. VFP9 presumably runs it as procedural code so no objects have been created.
Andrew

 

[Mike Gagnon]

Andrew

Can I ask why you do not translate the code to VFP9.0?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[andrewlee]

Mike,
Good question ! Actually, that's what I am doing. The FPW2.6 app is quite large ( just under 300 screens ) and has been running well for 10 years. My clients are demanding more functionality and also constant customisations.( As they do eh ? ) To cope with all this, I am doing a gradual migration to VFP. I have a project in VFP made up mainly of the .sprs that are generated from FPW2.6. By running these under VFP, it allows me to insert VFP functionality like Excel and Outlook automation,easy use of Shellexecute,Email etc. This gives my clients what they want now, without them having to wait for a whole rewrite which will take me about 12-18 months. I am re writing each screen using the proven procedures and functions from the original .spr which reduces testing. As each new form is completed it is added to the project and the .spr is deleted. My model is similar to that detailed by Chuck Urwiler's migration article at

http://foxproadvisor.com/doc/05239

It puzzles me that the app has been running fine under VFP6 and VFP8, but any FPW26 coded screens that have 2 listboxes, with the 2nd refreshed by the 1st, will not refresh under VFP9.
I guess those screens will now jump to the top of the conversion list.
Andrew