Received : 2007/08/15 20:55:10
Message : I have started to evaluate Aspose.Pdf.Kit and have run into the a problem with combo boxes. It seems that the demo code works but not completely. The document is updated and when I open the new document Acrobat 6.0 the data is in the dropdown. It is white text on a blue background. However, when I click or tab into the field the value disappears. This does not happen with the filled in textboxes. In Acrobat 8.1, the document fields appear blank. I do not think this is a problem with the versions of Acrobat. I think this is a problem with how the data is saved in the document. Any help is appreciated.
I have tried this new dll with the same result. The combo box values do not appear in Acrobat 8.0. I don’t know if it matters but this new dll is compiled on the 1.1 runtime. I am using the 2.0 runtime of .Net.
tmpPdf = New Aspose.Pdf.Kit.Form(aTemplate, aTempDir + "\" + CStr(aResultSet.Description)) For Each keys In tmpPdf.FieldsNames tmpRowArray = bd.Select("FQ_XML_NAME LIKE '" & keys & "*'", "FA_SEQ") For Each tmpRow In tmpRowArray Select Case tmpRow.Item(3).ToString Case "Check-box", "Radio-button", "Drop-down list box" If UCase(keys) = UCase(tmpRow(7)) Then If Not tmpRow.IsNull(1) Then If tmpRow(1) = "SELECTED" Then DDLText = Trim(tmpRow(5)) Try tmpPdf.FillField(keys, DDLText) Catch ex As Exception Throw New System.Exception("Field failure:" & keys & " in " & aTemplate) End Try End If End If End If Case "Multi-line text box", "Single line text box" If UCase(keys) = UCase(tmpRow(7)) Then If Not tmpRow.IsNull(1) Then DDLText = tmpPdf.GetField(keys) If Trim(DDLText) = "" Then DDLText = Trim(tmpRow(1)) Else DDLText = DDLText & Chr(31) & Chr(11) & Trim(tmpRow(1)) End If Try tmpPdf.FillField(keys, DDLText) Catch ex As Exception Throw New System.Exception("Field failure:" & keys & " in " & aTemplate) End Try End If End If End Select Next Next tmpPdf.Save()
We have found the reason of this problem. It lies on the interpretting syntax for Combo Box within different Adobe Reader versions, as we estimated before. This will be solved in about two or three days and the newest release will contain the hotfix.