Saturday 5 January 2008 @ 10:29 pm
There may be a bug in CR 2008 that fails to read previously available Custom UFL Functions. I have tried this on two separate PC’s that have multiple versions of CR installed side-by-side and get the same result. In CRv12 the node for Visual Basic user functions (u2lcom.dll) doesn’t show up in the function tree under “Additional Functions”. However on that same PC those functions do appear in all previous versions of Crystal. I am also checking in with some colleagues who (so far) are finding the same behavior.
If you get a different behavior please let me know. And if your reports rely heavily on UFL functions you may want to confirm that your functions work in CR2008 before you lock in on the upgrade.
The dev team has looked into this and the bug is caused when an older version of u2lcom.dll exists in either Windows\System32 or Windows\Crystal on the users system.
There are 2 potential workarounds:
1) Create an environment variable called “CRUFLPATH” and the Crystal Reports 2008 installation location of u2lcom.dll to this variable. For example in a default installation this would be:
C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86
2) Remove the u2lcom.dll from Windows\System32 or Windows\Crystal
This is expected to be fixed in the first service pack to Crystal Reports 2008 that is planned for late Q1 2008.