I have a cystal report that was created by another developer. He has since left our organization and I am having trouble running it from within our Visual Basic 6 application. We are using SQL Server v. 7.0 and Crystal Reports v 4.6 (The version that shipped with VB6). We are using NT Authentication with our SQL Server database.
The developer who created the report used a DSN (either a User DSN or a Machine DSN) to connect to the SQL Server database. (I have attempted to connect to our database using the SQL OLEDB interface in Crystal Reports, but I get a message stating that Crystal Reports is currently in use and I need another license to access the report writer -So I guess we are stuck with using a DSN).
If I launch the report directly in the Crystal Reports application, it runs fine.
The application that will be using this report will be distributed to 100+ users, so we don?t want to set up a DSN on each client PC. I created a File DSN on my client, and after multiple attempts to Add the Database to the report and to Set the Location of the tables, I successfully launched the report from the VB6 user interface. When I move to another PC, however, I am unable to launch the report. When I drop down the Database|Add Database to Report menu on my client, select the Directory as q:\EB DSN (the location of my File DSN on the network) then click on the
Can anyone help me with this problem?
