Andrew MacNeill - AKSEL Solutions

I've worked with out-sourced developers from other countries and recently had a situation that had me completely dumbfounded until I found it. In our user table, we stored encrypted passwords. When I ran the system using a standard startup process, it recognized the passed password without a problem. Then I ran it with an automated scheduling tool and it came back with an invalid user. So then I ran the automated scheduling tool directly from within FoxPro and it worked. I put code coverage on it, I put in message boxes and tracking (since you can't really bring up the debugger from within a runtime app) all to no avail. The passwords used in the development or standard approach simply didn't match the ones from the automated scheduling tool. What could the problem be? I knew it had to be the codepage . I tried checking the various code pages on the open files. They all appeared to be the same but then I saw the problem. The automated scheduling tool was including its own C...