Long Comment is being truncated

I am adding records to a table 'tblCallLog_Worksheet with this code:

'debug.print "Loading the Output Record"
'debug.print "wk_gComment"; wk_gComment
'debug.print "insertComment"; insertComment
'
Dim wkBRT As Long
Dim wkPropertyID As Long
'
'Debug.Print wkComment
'
'
'///////////////////////////////////////////////////////////////////////////////////////////////////////////////////
'

Dim rsOut As ADODB.Recordset
Set rsOut = New ADODB.Recordset
rsOut.Open "tblCallLog_Worksheet", CurrentProject.Connection, adOpenKeyset, adLockOptimistic
'
Dim rsIn As ADODB.Recordset
Set rsIn = New ADODB.Recordset
rsIn.Open "tblSelectedBRTsToProcess_Local", CurrentProject.Connection, adOpenKeyset, adLockOptimistic
'
If rsIn.EOF Then
    Exit Sub
Else
    If rsIn.RecordCount > 0 Then
        '
        rsIn.MoveLast
        rsIn.MoveFirst
        '
        While Not rsIn.EOF
       '     '
            wkBRT = Nz(rsIn!BRT, 0)
            wkPropertyID = GetPropertyIDFromBRT(wkBRT)
            '
            With rsOut
                .AddNew
                    !BRT = wkBRT
                    !PropertyID = wkPropertyID    '  = 0          
                    !CallLogHdrID = insertCallLogHeaderID
                    !User = insertUser
                    !DateTimeAdded = insertDateTime
                    !Comment = insertComment
                    '
                .Update
                '
            End With
            '
            rsIn.MoveNext
        Wend
            
    End If
End If
'
rsIn.Close
Set rsIn = Nothing
'
rsOut.Close
Set rsOut = Nothing
'

Open in new window


This is about as simple and straightforward as it gets.  The issue is that long comments are being truncated when added to the output file.
I attached the layout of the output file

I have the debug.prints (currently commented) above the code that adds the record to the output table.   The debug.print showed the contents of the filed 'insertComment' contained the entire comment.  However, the record created has the comment truncated.  The 'Comment' field in the output table is defined as memo.

Anybody have an idea of why the comment is being truncated?
TableDef.doc
LVL 1
mlcktmguyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ryan ChongBusiness Systems Analyst , ex-Senior Application EngineerCommented:
what's the data type of field Comment in table: tblCallLog_Worksheet ?

it seems that the field's length is not enough to handle the data that's why it's been truncated.

you may change the data type of field Comment in table: tblCallLog_Worksheet to Memo and try again.
mlcktmguyAuthor Commented:
As shown on my attachment containing the file structure, the field is already defined as Memo.
Ryan ChongBusiness Systems Analyst , ex-Senior Application EngineerCommented:
how was the truncated content looks like?

is there any characteristic you can identified from it?
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Robert ShermanOwnerCommented:
Can you tell if the comments that are getting truncated are all truncated to the same length?  And if so, what is that length?
Robert ShermanOwnerCommented:
Also, since you have two recordsets (one in and one out) way below where you have your debug.print statements, I'm curious where the comment is coming from?   I would place the debug.print statement right before the line that sets the !comment field for clarity.
Gustav BrockCIOCommented:
I haven't seen this with DAO, so you could try to convert your function from using ADO to DAO.

/gustav
Robert ShermanOwnerCommented:
Another possibility:  If you are seeing the truncation only in the destination table, which I think is "tblCallLog_Worksheet" according to the original question:

Go into Table Design mode on that table, and check the properties of the Comments memo field.  Make sure there is nothing under Format.  

In essence, many operations that require any kind of processing of a memo field may cause Access to truncate that memo field so that the operation is working on a computationally reasonable piece of information.  Things like sorting, grouping, indexing, some concat operations in certain situations might force Access to truncate the field.  

I still would be interested in knowing if the truncations are all happening at a specific length.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Robert ShermanOwnerCommented:
One last thought...  right after your ".update" on line 44, if you add a debug.print !comment on the next line, are you seeing the truncation there?
mlcktmguyAuthor Commented:
Thanks for the ideas, I had to set this aside temporarily.  I'll check out the ideas and get the information that's been requested this week.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.