Hi Mark,

You know that I generally don't participate in these types of threads (or it's cousin "MS isn't doing enough to promote VFP"). In this instance I'm making an exception because I think I might have something to say that you and everyone else might want to consider.

Before doing so, I think that the person who started this one is probably a victim. A victim of what? Bad information. They've probably heard a rumor or read something from someone who flat out didn't know what they were talking about. As such, shouldn't we simply point them in the direction of the correct information and be done with it, rather than bemoaning "Another VFP is dead" thread? I think that's a far more positive course of action.

Isn't there an FAQ on this subject? If not, perhaps the time has come to create one with the appropriate links.

Now please consider the following:

In 1992 or 1993 Microsoft introduced 6.0. As you'll recall it came with a disk compression utility called DBLSPACE. Shortly after its appearance, reports in the press stated that DBLSPACE was buggy.

At this point we should recall that DOS was Microsoft's "bread and butter" much the same way Windows is now. It would stand to reason that if these reports were inaccurate, MS would do everything in its power to disprove them.

Now if everyone who, to this day, believes that DBLSPACE was buggy, posted in response to this (please don't), we'd probably break the 1,000 post barrier with ease.

Here are the facts: DBLSPACE wasn't buggy. Much of the loss of data attributed to it was actually caused by people using the SMARTDRV caching program (with write behind) and failing to flush the cache (with SMARTDRV /C) prior to turning off the computer. Flushing the SMARTDRV cache had been recommended in DOS 5.0. The remaining instances were caused by unusual computer configurations. Despite much testing, MS was never able to replicate these. Further, statements both from MS and the computing press pointing out that DBLSPACE wasn't buggy abounded.

Doesn't all of the above sound awfully familiar? Once bad information gets out there, it's difficult, if not impossible, to get the situation corrected. Whether we like it or not, these types of threads are going to continue to appear. We should keep in mind that the original poster is a victim, and treat him or her as such. Point them in the direction of the correct information and be done with it.

That's my take on it.