Crystal XI.2 and Progress 10.1b creates 3-part table qualifier

[CrystalLion]

Despite the indication in the Crystal Reports comptability matrix which indicates that XI.2 reports can be run in versions 9 and 10, I am having the following problem.

I am writing reports against Progress 10.1b. I am using Crystal XI.2. I send the reports to clients who are using v9 or v10. When they try to run the reports they receive:
Failed to Open a Rowset.
Details: 42502.....[Progress]Table/View/Synonym not fould. (7519)

When I view the SQL query (Database\Show SQL Query), it displays a three part table qualifier, e.g "FOUND"."FOUND"."sql_Profile"...as opposed
to "Found"."sql_Profile"

I heard back from Progress support and they say it is a Crystal issue. That most likely Crystal will have a registry entry or similar work-around. I have not been able to find anything on the Business Objects site.

Any thoughts? Thanks

 

[Tatertot45]

Very odd. I run CR XI 2 against a progress DB and i don't have those issues. I set up an ODBC (RDO) connection, and ahve not had any issues. I also have the same setup for CR9 on my machine and can run the same reports back and forth, although some of the formatting is lost. As for the third qualifier, the only thing i can even remotely think of is a setting in the "Database" tab in the "Options" Menu option (under "file"). Maybe there is a roque checkbox marked or something.

Doubt i've been much help, but that is all i can think of. Also, there is a Synonym check box in the DB Tab, like i describe above. Is it possible that CR is looknig for a Syn., not finding it and erroring out? it might be worth a look.

 

[CrystalLion]

Good thoughts and I checked them out. I think the difference between your situaltion and mine is the version of Progress. Mine is 10.1b. What version are you using?

Thanks

 

[Tatertot45]

To be honest, i don't know. I had some issues with progress and CR when i first started, so we built a Datawarehouse. That has helped tremendously. Becuase the DW is SQL, I have had no issues with CR or Anyview IDS, which i administer. We currently run Syteline, off of the Progress DB and we are getting ready to upgrade to the latest version. Upgrading Syteline will allow us to go to a SQL DB, rather than Progress and i'm counting the days down.
You know, now that i think about it, i did have issues with CR and Progress. It had to do with the way Progress named the tables, and CR reluctance to accept hyphen/periods in table names. There is a setting in the "control panel", "Administrative tools", "System DSN", Select the DB "Configure". I remember seting the "Default Isolation Level" to "Read uncommitted". That seemed to fix a few bugs for us. Give that a try and see what happens.