Hi Barbara,

I am using pessimistic buffering because of the application and the person I am working with thought it would be better in this case. The application is a 9-1-1 Emergency Medical Services cardiac arrest tracking software that the Med Control Officer enters data some in real-time and some after the incident (cardiac arrest follow-up). So we didn't want to chance the Med Control Officer losing any data that he just entered while talking to the paramedics.

But I agree, optimistic is certainly my preferred choice. I am not a pessimist anyway. I have always been and optimist and always will be.

I am so close to getting this thing working perfectly, but for some reason when I add a new record and then go back to the new record and try to modify the record, it thinks another user is still using the record (in other words, it's locked) and that's running single-user standalone. But outside of that problem, I have it working beautifully in a multi-user network sharing environment with update conflict checking and all. So I am still scratching my head as to why some records are locked and majority are not. All records are processed the same way using the same code.

I'll keep thinking. I have read five Visual FoxPro books on the subject and think I understand this stuff, but something is not right somewhere in my code. I will be happy when this one is resolved.

Thanks for the feedback.