Thanks for all your replies - especially Géza Bartha who put me on the right track

I have now modified my ODBC configuration to the set MAX VARCHAR to 650 (it was originally 255), and this has now fixed 

the truncation issue.

See the attached images.

Does your application override the of_LoadPredefinedMsg function in n_cst_error?

If not (and if you have not made changes to this function in the ancestor object pfc_n_cst_error), then the following code is executed to load the messages:

// If appropriate, create the datastore cache.
If IsNull(ids_messages) Or Not IsValid(ids_messages) Then
   ids_messages = Create n_ds
   ids_messages.dataobject = 'd_definedmessages'
End If

// Reset the datastore.
ids_messages.Reset()

// Retrieve data into the datastore using the appropriate input source.
If is_msgsrc = DATABASE Then
   ids_messages.setTransObject(itr_msgdb)
   If ids_messages.Retrieve() >0 Then
      Return 1
   End If
ElseIf is_msgsrc = FILE Then
   If ids_messages.ImportFile(is_msgfile) >0 Then
      Return 1
   End If
End If

Return -1

This code will use the PFC-supplied DataWindow "d_definedmessage", which limits the message text to 255 characters.

So, like Miguel, I'm confused about your comment regarding an override "window" named d_crs_sys_messages". ???

Have you used the PB Debugger to see what the PFC Error service is doing, if the message is truncated at 255 characters? I think there is more going on here than what you have disclosed or communicated.

Further information - thanks for all your replies - :

Attached are 2x images - one of the message truncation showing in a response window,

and the second is of the postgresql ODBC settings

This is just "a guess" but maybe the following is what's happening to you?

If you are using the PFC messages table, then there's a datawindow called "d_definedmessages" in pfcapsrv.pbl and maybe also in pfeapsrv.pbl or any other layer of inherited classes you use with the pfc.
The field length for the 'msgtext' field is 255, so that would mean a truncation that is taking place. Maybe the table you are using has been altered to allow for more characters, but the d_definedmessages would have to be modified too.

source code in d_definedmessages:

column=(type=char(255) update=yes updatewhereclause=yes name=msgtext dbname="messages.msgtext" )

Doing a search on its use:

 ---------- Search: Searching Target client_cq for 'd_definedmessages'    (03:44:17)
 ---------- 2 Matches Found On "d_definedmessages":
pfeapsrv.pbl(n_cst_error).of_loadpredefinedmsg.0032:   ids_messages.dataobject = 'd_definedmessages'
pfcapsrv.pbl(pfc_n_cst_error).of_loadpredefinedmsg.0050:   ids_messages.dataobject = 'd_definedmessages'
 ---------- Done 2 Matches Found On "d_definedmessages":
 ---------- Finished Searching Target client_cq for 'd_definedmessages'    (03:44:17)

Hi,

It's not clear to me 'how', 'from where', 'when' you get this error message and 'when is the error message truncated' or how the odbc driver is implicated in this process.

Are you having the value in a string (with all the characters) and then when using the pfc inv_error.of_message(...) function the text is truncated?

Please give us a bit more information.

regards.

I failed to mention that we are using the pfc libraries - so its using the default pfc error behaviiur.

We have converted from Informix to Postgresql and the error messages displayed fully under the Informix ODBC driver. But are being truncated with the postgresql ODBC driver.