I know, I know :o) In the past ( I should say REALLY in the past) when I used to develop in FPD26 on a pc but compile it under DOS or Unix depending on what OS it ran on (we used to have 17 SCO systems), I used _DOS and _UNIX to determine which OS or version I was compiling under throughout my app. However, this app was already in place when I joined the team and it was determined by others to use the longer #IF VISUAL $ (VERSION()) check and for consistency, it continues...I'm just a single pea in pea soup here...


>>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,
>
>I know you have the answer already, but you could make the code shorter by using

#IF _DOS
>  * DOS Code here
>#ELSE
>  * VFP Stuff here
>#ENDIF

Of course, if this also has to be done for FPW then it doesn't work.