Does anyone know how to implement GE's custom UFL "U25mlif.dll" on a local machine for use with Crystal Reports? Many times we're trying to troubleshoot a report and we get the message that some formulas will fail to compile because of missing libraries. Then we try to run the report and a number of formulas error out because U25mlif.dll is missing.
I've copied this file from the Centricity app directory into both my Crystal app directory and the Business Objects bin directory. No improvement. I've tried registering them with regsvr32.exe - both generate an error. Crystal sees the functions contained in the other two U25*.dll files in those directories, but not this one.
Anyone got a clue?
Did you get it in the right place? In my notes I have written down to put u25mlif.dll into the following directory on the Crystal Reports machine:
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\jre\bin
To be honest I can't remember if I ran the GE reports as-is or if I replaced their data source with a 32-bit SystemDSN data source. Another note I have, and I think this was in reference to replacing data sources, is:
-Turn off Smart Linking under File->Options->Database->Smart Linking
We don't have that path on our machines. The closest we have is either:
C:\Program Files (x86)\Business Objects\Common\3.5\bin
...or...
C:\Program Files (x86)\Business Objects\j2sdk1.4.2_08\jre\bin
...and neither of those works.
The data source wouldn't matter because I should be able to access the functions in a new report as well. But the DLL doesn't appear under "Additional Functions" in the Formula Editor.
It's been a while since I have tinkered crystal reports, so this may not be exactly accurate. I have the vague memory that it is possible to modify a crystal report that will be used by cps, OR it is possible to modify a crystal report so it can be run directly from Crystal Reports, but not both. Meaning that you have to modify the report beyond repair to get it runnable in Crystal Reports.
I think the following two steps are needed to make the report runnable:
1. Remove any references to u25mlif.dll. Often u25mlif is only used to pull a couple simple things like username/location from CPS. Edit the header/footers and remove any calls to u25mlif functions.
2. Replace the data source with a local 32-bit SystemDSN. Create the new data source on your local machine, then replace the data source in the Crystal Report. This step may require pairing up all the tables from the report to the new data source.