The information in this article applies to:
SYMPTOMSUnder specific circumstances where two columns are calculating default values, a stored procedure may not be executed rapidly enough resulting in default values being inserted into a table's fields instead of the data generated by the stored procedure. CAUSEIf the stored procedure that calculates the default value takes too long, a default of 0 is used for numeric fields. This is a result of a timing issue, and not a coding issue. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0b for Windows. MORE INFORMATIONThe following code, when run using Visual FoxPro 3.0, demonstrates the behavior noted in this article. After a few records, the program will fail with one of several error messages. Using Visual FoxPro 3.0b, this code runs successfully. Steps to Reproduce Problem
Additional query words: VFoxWin buglist3.00 fixlist3.00b fail
Keywords : FxprgTable |
Last Reviewed: December 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |