I use to use CR10 and recently upgraded to CR2008. When I add tables to a report it is appending a '1' to the name. So tablename of Orderheader becomes Orderheader1.
You are using an OpenEdge database correct? For some reason CR thinks the table name is not as specified so it auto-aliases the table name when using the Wizard or adding a table. Go into the properties of the table name and simply remove the 1.
If you edit the name manually and then save the report to a new report name. Close the designer and then open the report up again does CR append the 1 to name again when setting location?
This may be an upgrade issue so they may not fix it.
I don't have a Progress table here so I can't test it myself.
I attempted to rename the tables - taking the 1 off but it would not let me. I get Invalid argument provided. Details: The alias requested "Ordrheader", contains a combination of characters which is not considered to be valid.
Mmmmmm... Did you verify the database first and then try renaming it? There was another post where this worked.
Check your table and field names also, don't use shift characters, they are typically reserved characters and should not be used even if the DB allows you to.
If it still doesn't work what I suggest to is purchase a support case and get a Report Designer Engineer working with your to duplicate the issue. If it is a bug then you will get a refund and then we can escalate it to R&D to look into why.
Also check to see if there is a new ODBC driver available, CR 2008 dynamically queries the database to fill the table and field names. It may be an older driver isn't following the ANSII 92 standards.
Verify databse did not help. It allowed me to rename if I use all non-capital letters, which is weird. The official table name is a capital 'O' so I had tried just taking the extra 1 of the end and it did not like it. I think it is a bug if it won't allow capital letters.
I did the save and then reopened and reset datasource location and it appeared to keep the name without the extra 1.
It's a workaround but is quite frustrating. Does CR2008 always do aliases now and CR10 did not?
Note: We cannot use a different driver as Progress supplies just the one.
It's likely due to.... in CR 10 we were more relaxed on ANSII 92 standards but with time and to resolve all issues we now fully support the Standard. Previously a lot of the database drivers were not following the rules so we had to "hack" our code to fix their problem. No more, it was too much to maintain, they could change their driver at any time so it broke CR again.
The capital in the name was likely also causing problems. There are a few option either in CR Designer or the ODBC driver to make the case sensitive so it uses what ever is in the DB. But depending on the driver depends on if CR can use it or ignore it.
I think in this case you are going to have to make the change manually unless PG updates their driver and follow the standards. That driver is likely quite old now.
You could report it to Progress to see if they can update it....
Bottom line is it's not CR causing the problem, we just found the problem once we follow the rules.
It may be something we can fix but it is considered a minor issue, and potential not a CR bug, so it would likely take a long time to patch.
That is not the answer. If I add a table a second time it appends "_1". And actually would be Orderheader1_1 as the example of adding the orderheader table twice..
It is something different happening between what cr10 does and what cr2008 does.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.