>Function argument, value, or type is invalid

Is the code shown here perhaps in a project hook, and the hook is included in the project? Or does it perhaps reside in an exe which shares some code with the project being built?

I've had trouble with such things... a project which builds fine manually (but also from the command line) would fail when built programmatically. I've eventually set the project programmatically to have all the properties I wanted it to have, and then I'd set a separate instance of Fox to do the actual build:

oVfp=Createobject("visualfoxpro.application")
oVfp.DoCmd(Textmerge([build EXE "<<tcexe>>" from "<<tcpjx>>"]))

And the problems stopped. The remaining problem would be a stranded copy of Fox in memory, if the oVfp reference was left dangling, or removed before it was forced to quit, but that was in the beginning, before I learned how to deal with that and prevent the errors.

HTH

>>>project that works fine to build interactively fails using BUILD EXE or the prject.build method. I cannot find this anywhere, but I am wondering if "errors" like array not found could be the cause,.
>>>
>>>It does not seem likely or logical, as the user presses ignore all, and the errors are hamless. but I cannot figure out the issue. The build attempt returns .f. and creatss a small stub .exe. Here is typical code, in which to all apperances it works -- there is no discernable difference in the time or processing apperance between the interactive build and the programmatic build.
>>>
>>>MODIFY PROJECT foo1 nowait
>>> aproject = _vfp.Projects[1]
>>> aproject.versionnumber = blah
>>> aproject.versioncompany = blah
>>> aproject.versionproduct = blah
>>> aproject.versioncopyright = blah
>>>
>>> y = JUSTSTEM(aproject.name) + ".exe"
>>> z = aproject.build(y, 3 , .f. , .f.) && filename, type, rebuildall, showerrors
>>> aproject.close:
>>
>>
>>If you use aerror(), is there any error reported?