>>
>>Since you can't get Crystal Report to execute a function for you, why not do all the work on the VFP side and give Crystal Report a finished master cursor with all the results in it?
>>
>>José
>
>
>We are not calling Crystal Reports from within FoxPro; just the opposite. The Crystal Reports forms we are creating will access the FoxPro database via ODBC. Using a view is not really an option, because the functions which need to be performed on the data are user-defined functions (actually, a function library which we purchased). I can't really put them in as stored procedures, since the Crystal Reports application is to have as minimal an impact on the existing FoxPro code base as possible.
>
>As it turns out, we were able to work out a solution. The vendor who wrote the function also has the function available as a .DLL. We were able to write a Visula Basic "wrapper" around the DLL, coding it as necessary for the Crystal Reports UFL. The actual VB code was minimal; two DECLARES to the .DLL, and two functions to call the DLL functions. Something to keep in mind should anyone need to write UFLs for Crystal Reports.
>
>Thanks,
>
>Bill

I am glad you found a solution thinking outside of the box...

José