cancel
Showing results for 
Search instead for 
Did you mean: 

Error with Crystal Reports for Visual Studio 2008 Runtime and Windows 7 x64

Former Member
0 Kudos

Hi all,

I am currently estimating whether my company hand-crafted software is compatible with Windows 7 64 bits or not. The application was built with Visual Studio 2008, and initialy targeted to run under 32 bits OSes, .NET Framework 2.0 and Crystal Reports 10.5 runtime so far.

I was about to certify this compliancy when I discovered a problem with embedded barcodes in reports (using Azalea Software's user function library u2lbcode.dll with Barcode128A method), raising the worlwide well-known exception "UFL 'u2lbcode.dll' that implements this function is missing".

I'm figuring this issue is related to the folder where the library file is placed, that might be wrong. I already had the same problem with former versions, when migrating from Windows 2000 to Windows XP and .NET Framework 1.0 -> 2.0+ and fixed it by locating the u2lbcode.dll in the %system32% folder, rather than 'bin' folder. But it looks like I'm done with that trick. Welcome to x64 world! 😕

I browsed the net and documentation, found nothing valuable but the fact that CR for VS2010 is compatible with 64 bits OSes. Does it mean reversely that CR for VS2008 is not?!! Nothing refers to that possibility. Nor any updated documentation from former Business Object or Azalea's, spelling library file location requirements per OS/.NET Framework (last one was up to Windows XP...).

Upgrading the whole application to .NET Framework 4 and Crystal Reports for VS2010 is not a point. Definetly.

Does anyone have some precious idea/tricky workaround/knowledge on the subject that could make my cogs work forward again?

HUGE thanks in advance, cause this may cancel my company project of upgrading to Windows 7 x64 (VMs are not a point too).

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

I have seen this error when the barcodes from Azalea were used, but the then not installed on the runtime computer. E.g.; if u25azalea.dll is missing on that computer, but the report requires the dll, then the error will be thrown. Poss(?).

- Ludek

Follow us on Twitter

Got Enhancement ideas? Try the SAP Idea Place

Share Your Knowledge in SCN Topic Spaces

Former Member
0 Kudos

Hi Ludek,

I read the note you wrote about CR runtime support for x64 OS. The one I'm currently using is CR10.5 x64. I totally agree with your assertion regarding the presence of dependencies. My main problem is that I don't even know which folder to place libraries into. 😕

More than this, all these barcoded reports are running fine on 32 bits environment (including Windows 7), without any u25azalea.dll library, that is the new version of Azalea's library dedicated to .NET Framework 4.0. So, IMO, Azalea is responsible for this issue because they do not supply any x64 UFL library file for older frameworks than 4.0.

I'm afraid I must migrate to CR for VS2010, to be able to handle barcodes in reports using Azalea's x64 UFLs.

Thanks.

Jean-Yves

former_member183750
Active Contributor
0 Kudos

I wonder if the following from Azalea will help?

http://www.azalea.com/crystal-reports/

- Ludek

Answers (1)

Answers (1)

krscheffler
Advisor
Advisor
0 Kudos

Hi Jean-Yves,

If you can, you may want to move this question to this part of the community: http://scn.sap.com/community/crystal-reports-for-visual-studio

Crystal Reports for VS questions can be posed here.  If you can't move the question, then you may want to recreate.

Hope that helps!

Kristen

Former Member
0 Kudos

Done.

saurabh_pathak
Active Contributor
0 Kudos

Hi Jean,

You can definitely use CR for VS2008 on x64 machines. Refer to this document for more info:

http://scn.sap.com/docs/DOC-21528

What happens when you register the dll (u2lbcode.dll) at C:\Windows\System32 location?

Also provide the exact screenshot of error message (if any)?

~ Saurabh