Custom "include path" for UFLs

[Former Member]

Hi,

in older versions it was necessary to include UFLs written in C to "c:\WINDOWS\Crystal". Nowadays, "C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86" seems to be the appropriate path.

Is there any way to force CR to search within a different path? For example, I'd like my UFL to be loaded from the program directory of my own application.

Setup: .NET 2.0 with CR2008 SP2

Regards,

Florian

[former_member11696 · Accepted solution]

Hi Florian,

CR uses the location of the EXE, then the working folder specified in the Icon, then the Windows System folder then down the PATH statement.

So yes putting your UFL dll in your folder should work?

Also there is now support for full UNICODE strings in an updated UFL. I'll check if it's available on our download or sample site...

Did you try it and if so what were the results?

Thank you

Don

[Former Member]

> CR uses the location of the EXE

Does not work. The report won't load.

> then the working folder specified in the Icon

What "Icon"?

[former_member11696]

When you say the report won't load is this correct? The report should load even if it can't find the UFL. It will complain with an error in formula.

The Icon is the desktop or Menu icon of your executable.

If it doesn't work then you'll have to put it in our \Bin or win32-x86 folder.

Thank you

Don

[Former Member]

Yes, the report loads with a formula error, which causes the report not to display ("load").

I do not call the executable from a desktop icon, but start the executable directly. So the working directory is correct.

What do you mean with "if it does not work"? Shouldn't the behaviour be clearly defined somewhere?

In any case, it doesn't work. Can you consider the possibility to specify a custom include path or at least using the working directory as include path as a feature request?

[former_member11696]

What type of UFL is it? Is it written in .NET and therefore needs to be entered into the GAC? Or COM or u2l*.dll

We always specify the UFL to be in our \bin or where ever the u2lcom.dll or where crpe32.dll is.

Search the help file on UFL and it should specify where it is placed.

[Former Member]

As I already said in my original post, it's neither .NET nor COM, but a plain C/C++ DLL.

(And I did search the help file before. I do not ask questions for information that I can easily find in the help file.)

[former_member11696]

OK, then you have to put it in CR's folder structure if no where else is working for you.