>>>Thus, it does come down to the fact that if the project does not have Debug Info checked, the line numbers are not included. And this is what I thought at the top of the thread.
>>>
>>>I don't include the Debug info not because I am concerned about someone getting the source. I don't care. But the size of the EXE will be much greater. Currently (without the debug info) the exe is about 13.5 MB (13,5 for euro). I think I tested once including the debug info and the size almost doubled. Many of my users keep the exe on the server and load it from the desktop shortcut. Therefore, their load time will be doubled. Many ppl won't be happy.
>>
>>If most of your dev work is done in/with .vcx, you can handle a lot of the size problem with a special build step removing all source from the memo field of the .vcx after compiling with debug info(=line numbers) and before creating the deploy-exe.
>
>Thank you for the suggestions. I will consider it although I know that .vcx is not a majority of the app. Tons of .frx, and .prg too.

Makes me wonder what increases your deployment size that much. Anecdotal evidence puts source in memo to between doubling and quadrupling. Gut guess for line numbers alone between 10 and 15% increase, but I never tested/measured myself, only remember some agonizing (sober...) meetings where the same issues were rehashed ad nauseam by many talking heads, until a plan to give a tiny budget
(half of the total H of all talking heads in that meeting) to experiment to the then-second-in-command of deployment was given.

He had definite statistics and a clear plan of action 3 days later, became head of deployment and a friend later. But some talking heads were appalled that one of their issues was solved, esp. as was done not by talking ;-)