I created a simple report in the Crystal 2011 designer, selecting one column from one small table. I created one version connecting to Oracle via OLEDB, another version connecting to SQL Server via OLEDB (exact same database exept that one ran on Oracle, the other on SQL Server). When I change from Oracle to SQL Server at runtime using the .NET SDK, I have no problems. When, however, I switch the SQL Server version to Oracle at runtime I connect OK but then get an error "table not found". I used the exact same credentials as what I applied at runtime, so it's not a security issues. I inspect all the logon properties, etc. at runtime to make sure that what I set it to at runtime matched exactly the properties that were coming in from the report that was actually designed to use Oracle. Only thing I can think of is that the table name may not be fully qualified with the schema when you design in SQL Server but that it is in Oracle. But the table name / location / qualification seem to be read-only properties in the SDK. Any ideas on how to get around this?
Thank you,
Laszlo
