Conflict on SQL Server 2005 and Crystal Report

[sajankk]

Hi All,

I am using Crystal Report 8.0 and SQL Server 2005 for generating reports. I designed the Reports at home where i have SQL Server 2000 and Crystal Report 8.0 now I am trying to implement the same report in SQL Server 2005 but its giving error "unable to logon server".

I tried to remove the database from the report and added the database again from the 2005 server but here i am not getting SQL server in the list of System Database. Somehow i added through ODBC. but its not working and giving message 'database dll "" not found'.

Your suggestion will be highly appriciated.

With thanks and regards Sajankk

[si_the_geek]

Thread moved to correct forum, and duplicate thread removed

[techgnome]

REmove the connections.... use OLEDB.... then select OLEDB for SQL Server....

Enter the appropriate connection info, test connection, and it should work.

-tg

[sajankk]

Hi Thanks for the reply, i have already tried using OLEDB but the problem is the table name we used in crystal report is like 'Table HDFC 001' its having spaces in the table name, and after using OLEDB its gives a default table name like 'Table_HDFC_001'.

And i am also using many functions in the crystal report which is using the field name like '[Table HDFC 001].Field1'. Since the table name itself is changed its saying the invalid field name while showing preview.
And if i change the field name in function like 'Table_HDFC_001.Field1' its working fine.

And then since i was having SQL Server 2000 in my computer so i tried to give the same environment here and i installed SQL Server 2000, by installing SQL Server 2000 also its working fine without doing any change in the report or database.

But i have already defined many reports using field name like this '[Table HDFC 001].Field1'. Is there any option to do the same without changing the function or table name and without installing SQL Server 2000.

Your reply will be highly appriciated.

Thanks and regards
Sajankk

[techgnome]

Besides shooting the person who put those dang blasted spaces in the table names? Since you are working with SQL Server, have you thought about doing the queries in a stored procedure?

-tg