Getting UFLs to work

[sgo7]

I had CR 8.5 and a UFL, U2LCOM.DLL for calculating weekdays including holidays. This is displayed in the function editor under the additional functions label. When I upgraded to CR 9.0 on a Win2000 machine I no longer had this UFL show up. Clicking on Help, About, more info shows that U2LCOM.DLL is loaded, or at least there in the list, but it's not showing up in the function list like it did before. The DLL file is in the proper directory. I'm inclined to think the problem isn't actually that DLL file but some other as yet unidentified missing file that is causing it to not display or be available for use. I installed from an UPGRADE disk, but uninstalled 8.5 before I did.

Any ideas? I've beat this one to death to no avail and the CD tech support has not even given me a clue.

 

[rebel11409]

Check your windows registry settings.

I'm looking at the instructions for some UFL's I got from
the Crystal website yesterday and they note the UFL must be registered in windows before the functions are made available.

 

[chelseatech]

Because CR9 can installed side by side with earlier CR, the folders with the UFL's are stored elsewhere

The registry entry.
HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\9.0\Crystal Reports

says where that folder is located. You might like to put your UFL there and regsister it.
Editor and Publisher of Crystal Clear

http://www.chelseatech.co.nz/pubs.htm

 

[sgo7]

Thanks for the suggestion. Actually I got it fixed. As I said in my original post U2Lcom was loaded which means it was correctly in the registry. My point about suspecting some as yet unidentified file as the problem turned out to be exactly the case. The way the function was listed in the function editor had me believing that u2lcom file was responsible for the function because it was listed as (U2LCOM.DLL), parens and all right after the function. As it turns out the actual missing file was cruflwdays.dll. Once I sent a screen shot to CD tech support they pointed me to look for a file named cr*.dll. Once I did that, all I had to do was to copy that dll into the correct folder and register it. I was whole again. Apparently the u2lcom file only acts as a server for the actual function -- or something like that.