Hi Mike,

I understand your position about doing a service posting some code. I am sympathetic. But I'm hoping that you can understand my position.

I have already identified what needs to be done to ensure that the security flaw can be overcome. I've identified the registry keys and the FFC class library that can be used in inline code to check and/or change that registry value. It can be done in a few lines of code using the registry classlib. Honestly, it's that simple!

However, I won't post that code. As a Microsoft employee, any code I post is "code from Microsoft". Posting code that tweaks a registry entry covered by an official security patch is not something I'm comfortable with.

I'm truly sorry about that limitation, Mike, and I will be more than happy to help you arrive at your own solution and I would hope that when you do you share that solution with others.


>You would be doing us all a service by posting the small piece of VFP code needed to avoid propagating this security flaw when distributing VFP6 runtime applications. Surely no one would have reason to find fault in an inconsequential deviation from the current patch, which is known to be inadequate.