>>>>I use FoxFire mainly for end-users to be able to create their own without a lot of hand-holding from me. Otherwise, I use the VFP Designer. I think it works fine as well. I just finished a very detailed Government form that uses extensive UDF() calls, dozens of boxes, almost 100 fields, 5 different tables, and generates very fast when called. Of course I use a form subclass to set all of this up. It took about a week to create this, near blindness and a couple of severe headaches because of the detail and the small fonts required. But it works great.
>>>
>>>From my experience, the users who demand the possibility to create their own reports in most cases never use it. :) I also use UDFs extensively, for example for calculating complicated totals through SQL SELECT instead of report variables.
>>
>>Hi Nick,
>>
>>I've given users the option to both modify reports (for the purpose of changing field widths, modifying distribution lists, etc.) and creating simple listings using the Report Designer since FPD 2.5. More complicated things, I have to do. Still, I've found that taking a little time to instruct them on how to use the Designer has saved me much time. Granted the Designer could use some improvements, but not from the end user standpoint. IMHO, allowing user's to create reports based on their own criteria is something for 3rd party products to do, not VFP. Of course, that's just my opinion. I could be wrong.:-)
>
>Hi George,
>
>I think you are right. Simple reports the users can do themselves in VFP report designer, but they usually can't do more complicated stuff wit ant custom report writer. Very often they even have a very little idea how the report should look like, and only after you figure something out by yourself - you know - they can tell you that what they see is not what they had in mind. (WISINWIW - What I See Is Not What I Want :)))
>
>Nick

DWIMNWIS

Do What I Mean Not What I Say

I used to hear that alot from my father.

Maybe we need SET TELEPATHY ON ???