Our company is definitively NOT planning to use it. My boss and I share the opinion that EVERY network is inherently unreliable.

Say Goodbye to free answers ... Or, "I can write the necessary code WAY faster if I know the context. So please 7zip the complete source of the project, and send it to me, together with the name of the company you're working for, and the name of the company that ordered the project."

The most surreal aspects of what I could contribute are in the problems, not so much in the solutions. Rewriting something letter-by-letter worked several times with me, too. And there were no hidden letters or non-breaking spaces in the original. In a VB6 program, we got runtime errors when the program was run under Windows XP, but not when run under Windows 9x/ME/2000. Most annoying thing was, the error was reproducible only in the compiled program, but never in the development environment. Took us weeks to find out. Turned out it was using modal dialog windows (from the MsgBox function) in the GotFocus event handler. I don't remember the fix we used, though. In VB6, the SendKeys function ceased to work properly under Windows Vista. So I programmed a function that performed the needed keystroke actions one after the other. The weirdest issue we ever encountered is the following, I think: Some clients from Switzerland got a "path not found" error when running one of our programs, but it worked fine with most clients. During tests with several different Windows versions, no problems of this kind were ever encountered. Turned out it were only French-speaking clients that got that error. But setting the system language to French didn't reproduce it. Luckily, we had an MSDN abo that time, so we could legally download and test a French Windows version (I don't remember whether XP, Vista or 7; maybe all of them). Here, the error suddenly was present. A short investigation revealed that the API call for a path "plenked", i. e. it put superfluous spaces before punctuation marks - and the backslash was a punctuation mark too, seemingly. (Note: in French, spaces before punctuation marks except the full stop are required.) Solution was simple: Remove all spaces immediately before and after backslashes in a path.

I've done something like that too. (And I confess I never cared to take it out of production code. At least I put a bit of comment besides it. And I put in a bit of information where this strange condition occurred, of course.) Sometimes we get errors because the programming environment behaves differently from what the documentation says, and they are among the errors that are hardest to find. And iirc, it was one of these cases when I put in that code (among tons of similar code elsewhere of course). (We even had several times encountered an error that occurs only in production code, but never in debug.)