I have several clients report this problem to me as well. After some testing it only seems to happen when the exe is "served" off of a WIN9x box. Moving the exe to a W2K or XP box and the error doesn't happen. I don't get this error with a VFP6 version of my app, only the VFP8 version is giving me this problem.

If any one has any ideas as to what is happening I would be interested in knowing. So far my clients have been alright with either rolling back the hot fix or moving the program to a W2k or XP machine.