Hi Eric,

Did you ever find a solution for this problem. I recently upgraded from Crystal Reports 8.5 to version 9 and I'm trying to access Fox2.x tables and I get the "Logon Failed" message when the viewer trys to display the report. This message occurs during the oleCRViewer.ViewReport() method is called.

I'm basically going through the same process you described where I set the new table location to the runtime location.

Any help on this would be greatly appreciated.

Thanks,

James



>The error changed to "Logon Failed" which is progress. <g>
>
>I'm not quite sure I understand this process. If I design a report using a 2.6 table named
>table1. I wind up with a bunch of Database Fields, Formula Fields, and Parameter Fields.
>The Database fields and formulas all have qualifying references, ie. table1.firstname
>
>If during runtime I tell Crystal not to use table1.dbf but rather _0PKHTBHTF.dbf using
>.SetTableLocation(), does Crystal resolve those references or is this my new problem?
>
>
>>Pass the second parameter as an empty string.
>>

>>oReport.Database.Tables(1).SetTableLocation(lcTemp,"", "")
>>

>>
>>>lcTemp = [c:\temp\temp.dbf]
>>>
>>>oReport.Database.Tables(1).SetTableLocation(lcTemp,lcTemp, "")
>>>
>>>Where temp.dbf exists as a 2.6 table, the above fails and says it cannot find the table. Any clues?