>It may be true, that the driver is poorly written; however, other M$ products such as WORD do not crash when referencing such poorly written software. With 7,000 users of our product, we get 2 to 3 calls a day from users asking why we (our product) crashes, and other programs do not. The problem has been acknowledged by M$, as being a problem in VFP 5, and 5a -- please don't apologize for what M$ doesn't apologize for. Further, M$ says "This has been corrected in Visual Foxpro 6.0.", they, the authors of the language, don't deny that the language has problems.

First, comparing VFP to Word is comparing apples to basketballs. It doesn't hold water.

Second, I am not apologizing for anything. I quoted from the same KB article you mentioned, and it clearly states where the problem lies.

Third, the statement that "This has been corrected in Visual FoxPro 6.0" is simply a statement indicating that the product has been made more tolerant of such poorly written drivers, not that there is a problem with VFP to begin with. If the drivers were written to spec in the first place then there'd be no need for the Fox team to expend their energy on such matters.

Finally, you may not like it, but the bottom line is that the fault is with the driver.