This is a discussion on CR9 and Providex within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> Here is what our database provider (Providex) is coming back to us saying: There is still an issue with ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Here is what our database provider (Providex) is coming back to us saying: There is still an issue with Crystal 9.0. For all versions prior the 9.0 Seagate Software issued a patch which replaced INNER join syntax with WHERE syntax, supported by the driver. Version 9.0 does not have such ability. >From our side we added a support for INNER joins in v.3.30 of the >driver and it works properly with all Crystals up to 8.5. For instance: SELECT * FROM {oj table1 INNER JOIN table2 ON table1.field = table2.field} Unfortunately, it does not work with Crystal 9.0 because they changed their INNER join syntax and a new syntax does not match the one supported by the driver. It is not the only issue with Crystal 9.0, poor performance is another one. Our MAS90/MAS200 team had discusscussion with Seagate Software and the decision was made to postpone using this version for MAS line of products until the next version of Crystal will be available. V10.0 is expected to be more stable and fast and much more backward compatible than the 9.0. In the mean time, if the customer has to use Crystal 9.0 the only solution we can offer is to create an SQL statement outside of Crystal 9.0 GUI and then to supply the pre-created statement in the run time. Does anyone know if this has been fixed? Please advise -- Posted via http://dbforums.com |