>>>>>Alas, it errors out before it writes the error file.
>>>>>
>>>>
>>>>Is it a long program? It is usually not hard to find a very long line of code, which may need to be splitted into several pieces.
>>>
>>>Only about 50 prg files and 3 dz forms. more reports than that. :(
>>
>>Are you saying that you don't know which particular prg file (or form) gives you the error?
>
>That is correct. The error dialog gives no indication of where the problem lies.

If this is VFP9, keep the debugger open, specially the output window. The pieces of code are echoed there as they are compiled, in the order as they appear in the .pjx. The last one is the culprit - or the next one that didn't get output. Just open the pjx as a table and find it, it should be one of those two.

> However, I have since found it. I started with all the files that have been edited since my last build and worked backward. There it was, a very long select statement. Interestingly enough, the prg ran ok when I ran it by itself, but it caused the error even when the file was marked as "exclude" and all of the code was commented out. Strange. VFP could certainly have been more helpful in this instance.

Mmm... you could have compiled all your prg files, and it would get its own .err file.