RTE 20599 when running C/Reps v7 from VB5 with ODBC, Oracle 8 1

[andymcd]

I keep getting this damned message (followed by "Cannot open SQL server", in a message box headed "Microsoft Visual Basic&quot after Crystal Reports has opened its preview window but before any data has been displayed there. Any suggestions welcome! It may, or may not, be coincidental that the SQL query in many reports developed using Access 97 and then given the "Convert Database Driver" treatment from PDBDAO to PdsODBC for use with Oracle, ends up with rubbish like "{oj "...."}" around the Join part, with Access-type "INNER JOIN ON" syntax. This all has to be rephrased by hand into Oracle JOIN syntax to stop ORA-928 errors. None of the above is consistent or predictable. I love Crystal Reports...

 

[balves]

This isn't really Crystal's fault. If you're going to change databases, you will often run into SQL that will fail on the new database. This is especially true if you point your Crystal report at a stored procedure. You'll have to fix up the SQL switching between SQL Server and Oracle, SQL Server and Informix, etc.

If you're going to create reports and forsee them running on multiple databases, I would probably choose ADO as my record source in Crystal. Then pass an ADO recordset from VB whose SQL matches the rules of the rdbms. Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer