Skip to main content

Burned by CodePages

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 CONFIG.FPW in the project.

For those who aren't familiar with this technique, if you include the CONFIG.FPW in the VFP project file, you can provide your own settings for startup, such as SCREEN=OFF and other settings.

The code had been written by a development group from the Ukraine and when I reviewed the CONFIG.FPW, it was marked with CODEPAGE=1251 and CPCOMPILE=1251.

As a result, any of the tables opened afterwards would translate the fields incorrectly. So the character that was stored as Chr(65) was actually being read by the automated tool as Chr(192).

Simple to resolve, but frustrating to track down - I KNEW what the problem was but I forgot they had included the CONFIG.FPW in the file.

In addition, it's a good idea to verify configuration files (like the CONFIG.FPW) when dealing with remote developers, especially from countries who will use different codepages. I've been in the position before when dealing with remote developers but most of them are North American. As developers start to share work with other developers around the world, be aware of the codepage issues.

Comments

Anonymous said…
Here's a requirement to include in the assignment for the contracter:
'ALLOWEXTERNAL ON'
must be put in the Config.fpw that's included in the compiled app
That way you can overrule all settings they are putting in there.

Regards,
Sietse Wijnker

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…