>Hi,
>I used to face to same prom before. VFP will report uniquesness error if pointer moved even in table buffering.
>As what I read from a book, it mentioned that it is VFP behavour, but it will not happen if your are manipulating view instead of underlying table.
Ah, I see, perhaps that is the problem.
The framework I use - at least with the features I use - forces the user to save or undo changes before moving the record pointer. Perhaps that is why I didn't encounter this problem.
However, I did want to show a clearer message than "duplicate record" (the framework doesn't say, duplicate based on what field(s)), so I created a small function to check for duplicates according to a specific index - and used it before trying to TableUpdate().
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
