Report with 2 data sources (TTX) & VFP memo to recordset problem

Question

Dear All,
I work on this for a few weeks, but still cannot fix it. Please help.
I use 2 TTX to create a report in CR XI. One table is do most things including grouping. Another table just contains 3 fields. Two fields are keys for left join with the main table, but it contains less key than the main table. That is some key in the main table may not exist in this one. The third field is a Memo field in Visual Foxpro. Now the memo field cannot display.
I got 2 methods to convert the VF cursors  to Recordsets for reporting. The first one is creating a subroutine to convert the VF cursor by myself to convert VF Memo field to Recordset's adVarChar like:
oRst.Fields.Append(<fieldname>, 201, 2147483647)
This method didn't work
The another method is using VFPCOM, a COM object that download from microsoft. That can convert the VF cursor to Recordset. I don't konw the type of Recordset field converted from VF Memo using VFPCOM .However, CR XI got a field mapping dialog when I preview the report. But I cannot find the correct field in the dialog.
Could somebody help. Thank you very much.
Regards,
Antony

Answer 1

Hello, Anthony;
When you look at Database|Database Expert and choose the links tab, are the two .ttx files linked successfully?
You mention that there is a field in the main table that may not exist in the second one. Is that causing a linking issue?
The most common issue is the ADO recordset does not match the structure created in the .ttx.
There is a dll that will allow you to create a .ttx file from each recordset exactly as Crystal Reports will see it using the "CreateFieldDefFile" function. Search your Crystal Reports XI R1 (11.0) CD for the file "p2smon.dll". It will not install automatically but you can copy it into your System32 directory and use the functionality. e.g. "C:\Windows\system32"
It was designed for Visual Basic so the code used there is:
Public adoRs1 As New ADODB.Recordset
If CreateFieldDefFile(adoRs1, App.Path & "\ado.ttx", True) <> 0 Then
   MsgBox "Field definition successfully created"
Else
   MsgBox "Failed to create field definition file"
End If
If you cannot complete this step, I suggest opening a SAP Support incident and an engineer could so this step for you using your ado recordset saved as an ADO file.
Again in Visual Basic:
adoRs1.save "C:\Temp\adoRS1.ttx"
adoRs2.save "C:\Temp\adoRS2.ttx"
Then the two created .ttx files can be tested in the report to see if they can be linked and verified.
Elaine