>>>>>>Hi,
>>>>>>
>>>>>>When I build the .exe of my application, I usually do not include the source code. But I have one .PRG that seem to have a problem with a lot of customers. And I can't seem to find which line causes the problem.
>>>>>>
>>>>>>So, is it possible to include just one .PRG in the .EXE so that the error will show the line number of the error?
>>>>>>
>>>>>>TIA
>>>>>
>>>>>Not that I know of.
>>>>>Trust you customers?
>>>>>Try to figure out what they do (gives insight)
>>>>>Else you might add a counter var and increment this on critical / expected lines. Like in the days of yore. I guess you get some meaningful error log at least with disp memo.
>>>>
>>>>I am trying all that but so far I can't pin point the problem. This is why the next step in to include the Debug.
>>>
>>>Then you must trust your customer - and set the debug flag on.
>>
>>This nothing to do with trust. I don't care of anyone gets my code. I was concerned that if I check the Debug option, the .EXE file will be considerably larger. And the time to load it will go up as well. But I will have to do it.
>
>Should not make a difference. The file might be larger, but this is good compressible code. Just zip it. Or hope that your transport layer through the net will do it alone. Might be faster, because if the crap is transparent zipped, the time for this process is wasted when compressed by you.

I created two .EXE files. One appfile.exe without Debug and another one appfile_deb.exe, with Debug. Placed them both on the customer server. The main user has appfile.exe on her desktop. But she decided to take a day off today; so I won't find out till Monday. And if she still has a problem, I will ask her to start the application with the appfile_deb.exe. So, hopefully I will find out, next week, the cause of the problem or at least the line number.