Eljefegeneo
Still trying to learn
- Local time
- Today, 03:50
- Joined
- Jan 10, 2011
- Messages
- 902
I have a split DB
A table has a field named [ProgramNotes] where the designation "#deleted" has come up for two records. When I tried to reinsert the data from an old backend in this field it says that "Your changes cannot be saved because the field "ProgramNotes" has been updated by another user.
First of all, would this happen without any notification that another user was on the same record? And since I am not on the server copy of the back end but one on my desktop, why would this message in the paragraph above come up?
But aside from that, I figured out a way to correct this but want to make sure that I am doing it correctly. I compacted and repaired the back end (which always gives me dread to even think of doing this). The two records now show "################" in the field. If I delete this "data" if one can call this data in the errant record, then I can retype data from an old saved copy of the back end. I guess I should also ask what this "################" means.
So, (1) what happened and why, and can I do anything to prevent this in the future and (2) did I fix it in the correct manner? Any and all suggestions and comments will be appreciated.
A table has a field named [ProgramNotes] where the designation "#deleted" has come up for two records. When I tried to reinsert the data from an old backend in this field it says that "Your changes cannot be saved because the field "ProgramNotes" has been updated by another user.
First of all, would this happen without any notification that another user was on the same record? And since I am not on the server copy of the back end but one on my desktop, why would this message in the paragraph above come up?
But aside from that, I figured out a way to correct this but want to make sure that I am doing it correctly. I compacted and repaired the back end (which always gives me dread to even think of doing this). The two records now show "################" in the field. If I delete this "data" if one can call this data in the errant record, then I can retype data from an old saved copy of the back end. I guess I should also ask what this "################" means.
So, (1) what happened and why, and can I do anything to prevent this in the future and (2) did I fix it in the correct manner? Any and all suggestions and comments will be appreciated.