>>>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.
>>
>>And how much larger is the other one?
>
>The Debug exe is 26,641,011 and the Non-Debug is 17,575,273

Since the DOS days, one of the things that I'd done was to break up application into separate "modules" rather than using a single monolithic EXE -- mainly to address a few concerns that came about:
* Shorter compile time since we'd only have to recompile only sections of the program
* Installer was simpler since it reduced need to "chop" large files into pieces so that they'd fit on diskette
* Patching was easier since we'd only need to replace part of the program that needed repair,.
* Easier to customize the application.

Granted, this approach is not without its faults:
* Total size of program (size of all the separate modules) would generally be larger than single EXE.
* You're likely to take a performance hit from calls from one module into another
* You'll need to make sure you can get version information for *each* of the modules.
* There's a real possibility that on customer site you end up with missing modules or mismatch of versions of modules.