I think the problem is that the Table in which ur trying to save the record is already open by the user. Make sure that Table is closed when you try to save that recordand hopefully u wont have any problems. I hope this helps.
It is already open--the main form shows numerous fields from the table, including a small text box showing the memo field. When the user clicks into the memo field, I pop-up a form to give the user a full screen view of the memo field.
It works--most of the time. And I can't imagine how I could record in the main form without huge repercussions. But I shall run off and do an experiment. What if I do a Refresh immediately before presenting the popup to ensure the record it receives isn't dirty?
I'm having the same problem with my Access 2000 setup. My setup has a central DB with the table containing the memo field. THen I have local DBs on each client that accesses the central DB thru ADO. I have sporadic #error in my memo field in 1 specific table that I'm trying to figure out how it's happening ... Since all data manipulation is done local except for pulling data and writing of data what are the ways in which this corruption can occur?
just a guess.
can this be related to your record-locking scheme?
what error number are you getting (? 3260, 3197 ?)
...and maybe trap the error:
dim getInput as integer
on error goto err_conflictHandler
'your tidy-up code goes here
select case err.number
'do something intelligent - someone has edited the record since you opened it, probably best is:
msgbox "Record edited by another user: cancelling save", vbcritical, "Conflict!"
getInput = msgbox(err.description, vbretrycancel + vbcritical, "Conflict!")
if getInput = vbretry then
msgbox "Cancelling save"
msgbox "Record was deleted", vbcritical, "Cancelling save"
msgbox err.number & " " & err.description, vbcritical, "Unanticipated Error"