VB6, Crystal Reports 8, with SQL Server 2005

[roopjm]

I am working on an application that is developed in Visual Basic 6, and is using Seagate Crystal Reports 8 for reporting. The client wants the Database to be SQL Server 2005, however we have had some issues with our application and had to install SQLServer 2000 for the reports to work.

The issue was the "Physical Database was not found", and installing SQL 2000 fixed this problem.

Given that the client only wishes to use SQL2005, is there any way we can get these to work in conjunction without a code-base rewrite?

Thanks!

[Hack]

Welcome to DevX

In so far as SQL Server 2005 didn't exist when Crystal Reports 8 was released (and SQL Server 2000 did exist), I'm guessing that might be the problem.

Do you have, in your house, not your client's, the latest version of Crystal Reports that you could use as a test of this hypothesis?

[Phil Weber]

If you don’t get an answer here, you might try Crystal’s tech support site: http://support.businessobjects.com/

[jamesbandido]

how bout using odbc drivers that will allow older apps to connect to sql2005 ?

an internal office project we had (although it was in java), allowed us to connect to our newer sql2005 server without a code re-write ...

i remember the odbc driver we used was downloaded from the microsoft site itself ...

hope this helps ...

cheers !!!

[roopjm]

After several different research methods, I found that it was a SINGLE DLL was missing. If you run into this type of problem, make sure that you have

NTWDBLIB.dll in C:\Windows\System32\

its unable to be registered by regsvr32.exe

It's description is as follows:
Description: SQL Server Client Library
Company: Microsoft Corporation
File Version: 2000.80.194.0

I'm thinking it is a DLL from SQLServer 2000.
This works without any other part of SQL2000 installed.

Thanks again for your help!

[Hack]

It is in fact from SQL Server 2000. After googling the DLL, I found this on another site from a user with the same issue/problem.

"SQL Server 2005 does not include the files needed to do programming work on applications that use these APIs.

The recommended alternatives are captured in SQL Server 2005 Books Online in section "Deprecated Database Engine Features in SQL Server 2005", which can also found at MSDN at http://msdn2.microsoft.com/en-us/lib...,SQL.90).aspx:

Although the SQL Server 2005 Database Engine still supports connections from existing applications using the DB-Library and Embedded SQL APIs, it does not include the files or documentation needed to do programming work on applications that use these APIs. A future version of the SQL Server Database Engine will drop support for connections from DB-Library or Embedded SQL applications. Do not use DB-Library or Embedded SQL to develop new applications. Remove any dependencies on either DB-Library or Embedded SQL when modifying existing applications. Instead of these APIs, use the SQLClient namespace or an API such as OLE DB or ODBC. SQL Server 2005 does not include the DB-Library DLL required to run these applications. To run DB-Library or Embedded SQL applications you must have available the DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server 2000."

Thanks for coming back and posting your solution.

[SueNC]

I just wanted to say Thank you for actually naming the dll. I have searched on and off for about a month and everybody else just said you are missing the database dll, but never named it. I am using Crystal Reports 8.5, VB6, SQL Server 2008 R2 and the NTWDBLIB.DLL got rid of the error message "Physical Database not found". Thank you agian.