That's what I came up with too initially and I have since modified it to be at least the correct EXTERNAL command for the type. It's not needed, but it doesn't hurt...

>>Below is code in a VFP app that also runs in FPD26. The FPD26 version runs a screen and the VFP version runs a form:
>>
>>

>>#IF !'VISUAL' $ UPPER(VERSION())
>>	DO co_prnt.spr
>>#ELSE
>>	DO FORM co_prnt.scx NAME oco_prnt LINKED
>>#ENDIF		
>>

>>
>>One of my coworkers modified it to now be the below code:
>>
>>

>>#IF !'VISUAL' $ UPPER(VERSION())
>>	DO co_prnt.spr
>>#ELSE
>>	EXTERNAL PROC co_prnt.scx
>>	SET KEYCOMP TO DOS
>>	DO FORM co_prnt.scx NAME oco_prnt LINKED
>>	SET KEYCOMP TO WINDOWS
>>#ENDIF		
>>

>>
>>My question is why add the EXTERNAL PROC line? Isn't that NOT necessary in VFP? All functions running in the vfp8 form are contained in the form itself as properties of the form. I could understand a EXTERNAL FORM command if I was using macro substitution, but I'm not.
>>
>>TIA,
>>Tracy
>
>Tracy
>
>The only reason I can come up with why an External command is used, is to work with the build process. If the form is not included in the project, this forces it in on the next build
>
>HTH,
>Tracy