Visual Studio 2005 Application Failing to load DLL when Report Created in XI

[Former Member]

Post Author: roopjm

CA Forum: .NET

I'm creating an application that creates mailing labels and barcode labels, with Visual Basic .NET 2005

The client wants to use and create their reports with Crystal XI, and the application does not have a traditional database, merely one using an XML schema.

I can successfully create the report in Visual Studio 2005, and have the application run no problemI can successfully create the report in Visual Studio 2005, Open it and Save it as Crystal XI and have the application run no problem.But if I create the report in Crystal XI and try to run it from the Application i get the following error:"Failed to load Database information. The database DLL 'crdb_xml.dll' could not be loaded. Error in File <.......>"

I have all of the required files and dll's on my development machine.

Any suggestions and tips would be most helpful.

Thanks!

[Former Member · Accepted solution]

Post Author: Argan

CA Forum: .NET

Try recreating the report in VS.NET 2008. Right now, no other version of Crystal is supported with VS.Net 2008 other than the one that is bundled with it. So CR XI and XI R2 will not integrate and their runtimes can not be used.

[Former Member]

Post Author: jswift

CA Forum: .NET

We are on visual studio 2008 and fetting this error each time trying to load th report. We went to the fix and it did not work. HELP

[Former Member]

Post Author: jswift

CA Forum: .NET

We are on visual studio 2008 and fetting this error each time trying to load th report. We went to the fix and it did not work. HELP

[Former Member]

Post Author: Argan

CA Forum: .NET

Running reports that were created in a newer version of Crystal against older runtimes is not supported due to these types of issues.

They probably created the report using a connectivity dll that isn't available in the CR for .NET 2005.

Have them try creating it using the crdb_adoplus.dll instead, that is the one meant for datasets (just select the ADO.NET section in db connectivity instead of the XML section like they are)