I'm creating a new report using Crystal 2011 connecting to a Progress 10.1.C DB through an ODBC Connection. When I connect to the db and select the tables I want on my report it's placing a 1 after the table name when creating a new report (v_table1). In crystal XI the 1 at the end of the table name meant it was an alias. This is a new report so there are no existing tables on the report. Is there a reason why it's doing this? I have tried renaming the table from v_table1 to v_table but I get the following error: "The alias requested "v_table", contains a combination of characters which is not considered to be valid." Does anyone know why this is or how I can fix/get around this?
According to the Product [Platform guide|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10df8fed-5cc6-2e10-93a8-99c15c6de338&overridelayout=true] CR only supports 10.1b.
Typically CR will Alias all table names as of CR 2008.
For more info see this [kbase: 1216864 - Support information for Progress Database Software|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233313336333833363334%7D.do]
Is there a reason why you don't want to use the Alias?
I get the same problem/error when using Progress 10B.
The reason we don't want to use an alias is that it confuses our customers who work with our tables. There should be no reason that we have to use alias.
I also have a problem where I can't set the datasource location on an existing report that was created with Crystal XI, when I do I get a message saying "Some tables could not be replaced, as no match was found in the new data source. Please specify the table required for any unmodified tables." I then click ok and find the matching table in my new datascoure location and try to update the datasource location and nothing happens. it's not updating to use the new datasouce location so I'm unable to run the report using the new datasource location. Is there a fix for this?
I was hoping the problem would have been fixed with Crystal 2011, we didn't upgrade to Crystal 2008 because of this reason.
When I try clicking on your link of For more info see this kbase: 1216864 - Support information for Progress Database Software
I can't access that page.
The requested operation is forbidden for this resource. You do not have the permissions required to access this resource.
I know I've seen this before but I could not remember where or when... I did a search in our bug tracking system and I believe the reason why is two fold and I recall now the reasons...
First it's due to the "_" in your table names, when CR comes across Shifted character CR aliases the table names for compatibility which is why it always appends the number 1 onto your table name, because CR replaces the Shifted character with an underscore which you are using it appends the 1. Work around is to not use any of the shifted ( top row of the keyboard ) in your table or field names.
This is true for ALL DB sources.
Second the track I found refers to 10.1.b is no longer supported so it was updated to include 10.1C, platforms has not got the update.
ADAPT01515094 - Set Location Error caused by Aliases with Progress OpenEdge 10.1b ODBC Driver
It was fixed in SP2 which you can get from here:
Test again and see if that helps?
Then update your post with the results and either mark as answered or well keep going depending on the results.
Sorry I should have read more details.
There is a registry key you need to create We Introduced due to OpenEdge's ODBC API said it can't have same name for Alias with table name, but from testing, it can.
[HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database\ODBC]
If your client dll is other than listed above then simply use that name.
It may be tough now due to holidays and all...
Can you download ProcessMonitor from Microsoft and run CR and filter on crw32.exe. Then look to see if that registry key is being looked for and read? May be the patch was not installed completely or something else was missed...
If you need to you can always log a case, if you have a support contract or purchase a single case and Rep can work with you to debug the issue...
Back in December it was said that James had a fix for the problem of connecting to a Progress 10.1.C db using an ODBC Conncetion. Has that soultion been posted?
James tracked this and got it fixed. It should work, I've let James know it's not working for and he'll update the post shortly....
apologies for the delay in my response.
I worked with another Customer on this issue and they were successful in doing Set Location using CR2011 SP02 on a report created in CR XI with the steps documented in the knowledge base article "1618336 - Error setting location on a Crystal Reports XI report using the Progress OpenEdge ODBC Driver"
The steps outlined in the knowledge base are:
1) Upgrade CR2011 to Support Pack 02 which contains the modified crdb_odbc.dll
2) Edit the registry on the CR2011 machine to add key HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database\ODBC and under that key add string UseTableNameAsAlias and set it to PGPRO1019.DLL, PGOE1022.DLL
3) Use CR2011 SP02 to Set Location on the CR XI report
Please verify the ODBC driver dll in use by checking the Drivers tab of the ODBC Administrator as it may not be PGPRO1019.DLL or PGOE1022.DLL which will require a different value be placed in the UseTableNameAsAlias string in the registry.
AGS Primary Support
Global Support Center Canada
SAP Canada Inc.
Edited by: James Anderson on Mar 8, 2012 12:15 PM
please confirm the following info:
the config looks correct from the info you have provided. I have contacted IMS Development to look at this thread and see if they can see what I am missing.
In the meantime there is one unlikely thing you can try. Try putting PGOE1023.DLL all in capitals in the registry. I don't think this will make a different and I want to be sure.