I'm curious to see if the experts or anyone else can offer any explanation of the below Crystal behavior.
If a new report is setup and it uses several SQL Expressions but then later a new data source is added a message pops up stating to make sure not to add new SQL expresssions. The ones in place before adding the new data source still work even after adding the second data source. However, the option to work with the SQL Expressions just disappears.
The problem is that to make a change to one of those existing SQL Expressions, the second data source has to be removed (breaking the report in essence) in order to see the SQL expressions. Then the second data source has to be put back.
Is there anyway around this?
If a new report is setup and it uses several SQL Expressions but then later a new data source is added a message pops up stating to make sure not to add new SQL expresssions. The ones in place before adding the new data source still work even after adding the second data source. However, the option to work with the SQL Expressions just disappears.
The problem is that to make a change to one of those existing SQL Expressions, the second data source has to be removed (breaking the report in essence) in order to see the SQL expressions. Then the second data source has to be put back.
Is there anyway around this?