Charles,
are they compiled into the app? then ,no

I do something like

#DEFINE BuildAction_None				0									&& No Value
#DEFINE BUILDACTION_REBUILD			1									&& Rebuild Project
#DEFINE BUILDACTION_BUILDAPP			2									&& Build APP
#DEFINE BUILDACTION_BUILDEXE			3									&& Build EXE
#DEFINE BUILDACTION_BUILDDLL			4									&& Build DLL
#DEFINE BUILDACTION_BUILDMTDLL		5									&& Build MTDLL
#DEFINE dcBuildAction_Rebuild_Ext			'pjx'								&& Rebuild Project
#DEFINE dcBuildAction_BuildApp_Ext		'app'								&& Build APP
#DEFINE dcBuildAction_BuildExe_Ext		'exe'								&& Build EXE
#DEFINE dcBuildAction_BuildDll_Ext			'dll'								&& Build DLL
#DEFINE dcBuildAction_BuildMTDLL_Ext		'dll'								&& Build MTDLL

  lnBuildAction = BUILDACTION_BUILDEXE

 lnProjs     = APPLICATION.PROJECTS.COUNT
 FOR lnProj = lnProjs TO 1 STEP -1
  loProject = _VFP.PROJECTS(lnProj)
    loProject.BUILD(FORCEEXT(loProject.NAME,dcBuildAction_BuildExe_Ext),lnBuildAction,.T.)
 ENDFOR &&lnProj

Just turn it on and do documentation. ::)

Agnes

>In that case would blowing away the fxp files to force a recompile of prgs do the trick?
>
>>vfp will show this behaviour when daylight saving time "changes" and the source was compiled in the other "period". Just one of the "Duuhhh, what were they thinking!" moments for vfp I encounter twice a year ;-)