Brenda,

In the thread I reffered to there was shown a method to create report on the fly. For instance, you can create one template report with Field1, Field2, Field3, etc. Now you have table with different table structure, but the same meaninng, for instance, Field1 in this table is called myField1, Field2 myField2, etc.

You now can use the same report, but with the new names, if you select * to tempfile. and then do replacement.

I'm not sure I understand your UDF problem. If you put in detail line something like myUDF(), it would be calculated on each record and slow down the report (depending on how complicated the function is). Of course, your UDF should be either the separate prg in the path or in your procedure file, and you should set procedure to yourprocedure in the calling program.

UDF should return a value, which would be shown in report.

>I always get stuck on the little things. 1) Would my UDF be a variable? If so it wants to execute the UDF everytime I go to the next or previous page in Print Preview. I have the UDF at the variables Set Inital Value and Reset at End of Report, but still it executes in every page of print preview, which I do not understand or want. 2) my UDF is in something.prg. Do I just have to have something.prg in the same folder or somewhere in the PATH? Do I have to SET PROC TO something.prg? Because I do not think I can do that in my report.
>
>I do not understand the conversation about macro substitution. I think a simeple UDF to create the data source and then reference the alias.fieldname on the report would be the easiest.
>
>Thanks
>
>Brenda
>
>>>>
>>>I am not thinking too clearly but will try and explain.
>>>
>>>My clients need a report that is quite complicated. It requires a procedure to create the data source. All of my applications reports are built into the exe and I am not allowed to make changes to the exe at this time. But I still want to give them this report. My clients do have Query Maker, some third party software with some similarities to Crystal Reports, which they can use to build their own queries and then build their own custom reports. Query Maker uses the VFP Report Designer. I created a procedure as part of the exe where they can "import" and "export" their custom reports so that they can share the reports between sites. So if I build a report in Query Maker I can then export it and have them import it.
>>>
>>>Thinking that I can build a report that calls a procedure to create the data source and then all the fields on the report use that data source. So I need to get it all done with a frx, frt, and a fxp (I will sneak the fxp into the folder). I assume this is possible, is it? Any tips on how to get it done or any other ideas?
>>>
>>>Hope this makes some sense
>>>
>>>Brenda
>
>>>
>>
>>Brenda,
>>
>>This idea was discussed couple of months ago if my memory serves me right by Roi Ledford. The solution would be select into temp report
>>
>>pseudo-code
>>
>>select * from YourReport to tempReport
>>replace expr with strtranc(expr,"myReportField","myNewField"), ;
>>supexpr with strtranc(supexpr,"myReportField","myNewField")
>>
>>where strtranc - case insensitive strtran (here there were threads as well).
>>
>>That's just an idea, which you may consider.
>
>
>>
>Oops, my memory played trick on me. It was Rip Rynes...
>Forum: Visual FoxPro Category: Reports & Report designer Title: Macro Substitution(&) Thread #459993 Message #459993