So, working off of John's suggestion, I have actually walked through my form/code to find all fields that the DAO.Recordset Edit was causing the Runtime 3314 error. Luckily, there were only two that I encountered (so far). What I have done as a work around is setup two new String variables (since these are both Memo or MultiLine fields) and when the recordset is opened and the appropriate record is found, I set these variables to the existing fields in question. Then, during the Edit, I set these two fields in the recordset to equal the new variables. This way I am able to get around receiving the runtime 3314 error.
The bonus to this is that it also works in Access 2007 so for my users who are not going to be updated in the early stages, they will still be able to use the existing DB as well as my Access 2010 users (glad I don't have to manage two databases!) ...
Here is my "work around" code in case you need to reference it:
Code:
Set db = CurrentDb
Set recPar = db.OpenRecordset("Enhancement Request", dbOpenDynaset)
With recPar
.FindFirst "ID = " & ParID
If Not .NoMatch Then
ParStat = !Status
ParDetail = ![Detail Description]
ParBenefit = ![Benefit Statement]
If ParStat <> "Parent" Then
ParCmnt = "Yes"
.Edit
!Status = "Parent"
![Record Type] = "Parent"
![Detail Description] = ParDetail
![Benefit Statement] = ParBenefit
.Update
Else
ParCmnt = "No"
End If
End If
End With
recPar.Close
Set recPar = Nothing
Thanks again to John for getting me out of my cardboard box and taking a look around!