SQL Server 6.5/7.0 Compatability

[roboninja]

I developed some reports using a CR8.0/SQL Server 7.0 platform for viewing in a VB 6 project. The reports work fine on the development machine, but the client is using SQL Server 6.5
When a user clicks the menu option (or button) to view a report, nothing happens; no error, but no report either. I have tested it myself on another machine sporting SQL Server 6.5, and the same problem occurs. I am using ODBC to access the DB, and it work fine for all other aspects of the VB application. Anyone have any ideas? My only guess is that the reports may need to be tied to SQL Server 6.5 DB before being sent to the client. Any ideas would be great.
Thanks.

 

[kenhamady]

Have you tried it on a client PC with Version 7? This helps uncover if it is a client config problem or the version change. Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training/Consulting and a
Quick Reference Guide to VB/Crystal (including ADO)

 

[roboninja]

Everything worls fine on a client when SQL Server 7.0 is still the back end. I'm pretty sure it is the transition from 7.0 to 6.5. I haven't been able to find any info on Crystal's or MS's sites.

 

[kenhamady]

Are you using a DSN? Does that exist on the 6.5 with the same name as the original?
Tables and fields are identical?

There may be an issue switching versions, but nothing jumps out at me. One test would be to install CR on a 6.5 client and see if the sql7 report runs from the designer against SQL65 without modification. If not, that would probably highlight the problem.

Of course, someone who has actually tried what you are doing would be able to shed more light on this. Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training/Consulting and a
Quick Reference Guide to VB/Crystal (including ADO)

 

[roboninja]

Everything seems to be the same in both databases. I tried explicitly setting the connection property of the Crystal Report OCX, but that did not solve the problem. I'm totally out of ideas.

 

[kenhamady]

Try posting this in the Crystal data access forum, maybe someone there can troubleshoot it. Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training/Consulting and a
Quick Reference Guide to VB/Crystal (including ADO)

 

[roboninja]

Thanks. I think I found the problem. Even though the DSN was pointing directly to a specific database, it was prefixing the database name to the table names. The database name was different at the client site, so I removed the database names from the table locations, and it seems to work on a test system. Thanks for your input,