Ken,
I haven't had to set any delay yet-don't know why we havent' run into that problem either. We've got a few forms incorporated (we add them as we complete them). Here is an example of where we call the form in VFP and call the .spr in FPD26 (in this case it is a dos screen that calls a form or another dos screen):

*cn_menu.spr
#IF !'VISUAL' $ UPPER(VERSION())
	DO cn_prnt.spr
#ELSE
	* The hiding of windows and popup is necessary for correct screen
        * redraw after returning from the form in vfp and to ensure that
        * all modal windows called from the form are ontop of the screen 
        * and the form.  It presents a cleaner appearance.
        * The variables used are declared PRIVATE above this code.
        IF !EMPTY(POPUP())
		LOCAL lpPopup
		STORE POPUP() to lpPopup
		HIDE POPUP &lpPopup
	ENDIF
	IF !EMPTY(WONTOP())
		LOCAL lwWontop
		STORE WONTOP() TO lwWontop
		HIDE WINDOW &lwWontop
	ENDIF
	IF WEXIST('cn_menu')
		SHOW WINDOW cn_menu BOTTOM
	ENDIF
		
	DO FORM 'cn_prnt32'

	IF UPPER(TYPE('lwWontop'))="C" .AND. WEXIST(lwWontop)
		SHOW WINDOW &lwWontop
		ACTIVATE WINDOW &lwWontop
	ENDIF
	IF WEXIST('cn_menu')
		SHOW WINDOW cn_menu TOP
	ENDIF

	IF UPPER(TYPE('lpPopup'))="C"
		SHOW POPUP &lpPopup
	ENDIF
#ENDIF

Tracy

>Tracy,
> Including the FP2.6 Prgs and Sprs in the VFP7 project is what we do also. We have a routine that we use whenever we need to set _curobj (since that doesn't work well in VFP7). We also set a slight time delay (0.05 sec or so) when activating windows in screen sets since we've found that VFP sometimes won't activate properly otherwise. Fortunately all of our reports are in Frxs so we're ahead of the game there. Our only current problem is with the flaky list boxes.
>
>Are you running totally FP2.6 code within VFP or have you been able to incorporate some VFP forms as well? If so, how have you done this is I may ask?
>
>Ken Penrod
>
>
>>This is interesting. We have a huge FPD26 app that is in the process of being rewritten in VFP7. We have literally hundreds of screens and reports. In the meantime, we too are running the FPD26 code in VFP7. We have both an FPD26 exe and a VFP7 exe installed at our client locations. Most of our listboxes are populated by arrays also, but we have not experienced the problems you mention. I'll take a look at the code and see if there is anything not typical in our screen code. Right now it is installed at over 500 locations with few problems. The only major problems we have run into running these 'in between versions' of our app is that we have over 100 reports written using @...say and ?? which are in the process of being recreated in the VFP7 report writer. This is a major problem with GDI printers and printer commands. We had to do a lot of fixes in VFP7 to line up and clear the FPD26 screens which was done in the Dos screen editor using compiler directives to separate the
>>FPD26 code from the VFP7 code when necessary. We included the .sprs in the VFP7 project to run that code. During the upgrade process and while the screens are being redone in VFP7 as forms, we have to make any required modifications in FPD26 and then recompile it so the .spr is updated for the VFP7 project. I will really be happy when the full VFP7 version is completed, but it will still be months before that is done. We have different versions for different states that are all being merged into one version at the sametime (nightmare).
>>
>>Tracy
>>
>>
>>>Anyone out there have extensive experience running FP2.6 Win code under VFP 7? We've been running Mac 2.6 code under VFP 3 on Macs for several years but now have the need to run Win 2.6 code under VFP 7 due to FP's problems with USB/HP printers and other anomalies. I've handled all the timing issues when activating screens as well as the problem with _curobj not working but have an issue with list boxes sometimes not being refreshed by 'Show Gets'. We use list boxes populated by arrays throughout our app and in most places it works fine when you delete an entry and do a show get on it. However, in a few places when we delete an array entry it is not refreshed. When we add an element and reselect into the array it always works. Tis a puzzler.
>>>
>>>Anyone seen anything like this? Know of a website with tips and tricks about running 2.6 code under VFP?
>>>
>>>Thanks,
>>>Ken Penrod
>>>
>>>P.S. ...and, Yes, we are in the process of rewriting the app in VFP 7... although that leaves our Mac customers in the lurch.