>>>>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.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
