There are two rules for creating a UFL in VFP:

1. The name of the DLL must begin with CRUFL. This means that your project should also start with CRUFL. By default, the name of the project will be used for the DLL. I can't tell from your postings if you've done that.

2. You must declare the parameter and return value data types for the public methods. You've done that in your code.

The last thing to remember is that Crystal will read the registry when it loads, looking for CRUFL. If you build the DLL while Crystal is running, you'll have to Exit, then reload it.


>Craig,
>
>No I have not gotten ANY UFLs working. See my message #742535 for an example of a really trivial test UFL I cannot get to work. It was on a clean install of Win XP Pro (also Win 2K Pro), with clean installs of VFP7 and CR 9. Also CR 8.5 with latest (Jan 1) updates.
>
>All Crystal can tell me is that I must be doing something wrong, but nobody there understands or can test VFP.
>
>It is possible I am missing something in the UFL rulebook, but I can't figure out what. Since it seems to work for you, I would appreciate it if you could look at that simple test and see if I am missing something that is obvious to you.
>
>...Jim
>
>>Did you ever get UFLs to work in CR9? I just wrote one using VFP 7 and it works fine.
>>
>>