BUG: LOOKUP() Locates Deleted Records

ID: Q122511

2.50x 2.60 2.60a | 2.50x 2.60 2.60a | 2.50x 2.60a 

WINDOWS          | MS-DOS           | Macintosh
kbprg kbbuglist

The information in this article applies to:

SYMPTOMS

The LOOKUP() function locates deleted records even though SET DELETED is ON.

RESOLUTION

The only way to ensure that LOOKUP() will respect the SET DELETED ON command is to ensure that a TAG (regardless of its name) on the field being looked up exists. Please see the example in the More Information section of this article.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Program to Reproduce Problem

The following program demonstrates the symptoms. 

   CREATE TABLE temp (testfield c(10))
   INSERT INTO temp (testfield) VALUES ('FRED')
   INSERT INTO temp (testfield) VALUES ('WILMA')
   INSERT INTO temp (testfield) VALUES ('BARNEY')
   INSERT INTO temp (testfield) VALUES ('BETTY')

   GO 3
   DELETE

   SET DELETED ON
   ? LOOKUP(Temp.TestField, "FRED", TestField)
   ? LOOKUP(Temp.TestField, "BARNEY", TestField)
The second LOOKUP() should return a null string because the third record (the one containing BARNEY) should be hidden by the SET DELETED ON command.

Example Workaround

Insert the following command between the last INSERT command and the GO 3 command. Then run the program example again. 

   INDEX ON TestField TAG TestField
This time the second LOOKUP() returns a null string.

Additional reference words: FoxWin FoxMac FoxDos 2.50 2.50a 2.50b 2.60 2.60a buglist2.50 buglist2.50a buglist2.50b buglist2.60 buglist2.60a KBCategory: kbprg kbbuglist KBSubcategory: FxprgGeneral 

Keywords          : FxprgGeneral kbbuglist
Version           : 2.50x 2.60 2.60a | 2.50x 2.60 2.
Platform          : MACINTOSH MS-DOS WINDOWS

Last Reviewed: February 18, 1996