Cool! Don't worry, I'll make sure you pay me back sometime... If you see the description of the setting CLEAR, you'll understand why the update works: (CLEAR ) ON CLEAR data buffers after modifications
The first time I ran into it, it bugged the heck out of me. When I found out that it was because the answer was in "cache", I figured this had to happen all over the place, but strangely enough it doesn't. I have no clue why I've seen this only maybe 3 times in code (windows version 6.5 thru 7.6) in the long time I've been programming. It's a scarey thought when you assume that the software will always go out to the table to get current data ... But I had personally 3, but only 3, instances where it didn't. Wish I knew what made those instances unique. No clue about 9.1, haven't run into it yet. Karen > Karen - I owe ya big time! That was it. > I was just getting ready to unload and input the db as a desperate last > resort. > I'd thought PROPERTY... REFRESH, POST, CLOSE, OPEN and permutations > thereof would've worked forced a re-read of the table. > The fact that the BROWSE command made it work was a bit of a tipoff for me > but it would've been a while before I stumbled on using the UPDATE. > > While not a bug, it's an obscure anomoly IMHO. Does it still exist in > 9.1?
