Thanks for your reply. I played around with this past couple of days and I agree with your assessment as well. For anyone that are interested in knowing about this; the best practice would be as follow:
This function call ensures the integrity of your data in the event of validation or data refresh. So if your data need some kind of massage to it prior display or use in other operations afterward then I recommend to always call ResetCurrentItem () prior your data massaging.
If you call this after then all of your previous attempt will be wiped out :)
Main Topics
Browse All Topics





by: TheLearnedOnePosted on 2009-11-02 at 04:55:06ID: 25718885
ResetCurrentItem has a specific use, and I don't believe that you need to use it all the time. I have used it in the past, when working with a highly dynamic database project, and it involved detecting when the underlying database changed, and then refreshing the data.