>>>>I have found that under Windows NT you have to execute
>>>>SELECT tablename
>>>>=RLOCK()
>>>>UNLOCK
>>>>after a table update in order to view the "current" information.
>>>
>>>Larry;
>>>
>>>I tried your idea and got no change in the results. The machine I am on is a win98 os. Requerying twice is still the only thing that has found the records.
>>
>>How about issuing a SKIP after you delete, but before the requery?
>
>Larry; The SKIP worked. The idea of the record pointer being over a deleted record causing the strange behavior must of been correct. Locate didn't do it, I am not sure why, but probably a cdx thing. I am glad that someone else was able to recreate this, a programmer's sanity can be a delicate entity.:)
>
>thanx for you input
Glad to help. I didn't "recreate" the problem, it just seemed like the next thing to try. I guess that there may be a bug in the way VFP updates records or it may be with the requery...I don't know. It seems that the update trigger needs to fire before the record is "actually" saved and it doesn't fire until the record pointer is moved or the table is closed. Or, it may be tied to the way the browse windows work. What I mean is that if you have SET DELETE ON and delete a record manually in a browse window, you can still see the record until it scrolls of the screen...I'm rambling...anyway it's a good thing to know how to handle it in the future.
Best of luck.
Larry
//:^)