Hi Tore,

Basically you are suggesting for me to do what I thought VFPT should do <g>. Just kidding. Seriously, I understand the concept but probably will use the "packaging" to .EXE approach for now, simply because it would take less time to implement. Thank you so much for your suggestion (I might try it just to see how it will work, when I have more time).

>Hi Dmitry,
>
>since a frx is in deed a dbf, but with another expension, you can make do something like this, in semicode:

>use <somefrx>
>copy stru to masterfrx.frx
>use masterfrx
>add a field called reportname
>loop start
> lnRecord=recno()
> append from firstfrx && then secondfrx and so on
> goto lnRecord
> repl rest reportname with 'firstfrx'
>loop end

>Then to report you do like this:

>lcFilename=somename.frx
>use masterfrx.frx
>copy to (lcFilename) for reportname=yourreport
>report form (lcFilename)
>eras (lcFilename)

>
>All this is semicode, but I guess you understand the idea. You may have to change my semicode in order to create 'real' report.frx files.
>
>
>>I understand you that one way is to place all reports in a folder like "reports." But I think it does not look good when the customer sees all the 800 files (2 for each 400 reports). I think there is more "opportunity" for one of the files to get corrupted or deleted. This is why I was looking for a way to "package" all reports into one file.
>>
>>>why do you want to store the reports in the EXE?
>>>If there is a modification the frx file resiting in a subdictionary like "reports" is much better. You just change the file and you dont have to recomile the EXE.Different users can have one exe but differnt reports.
>>>reports can be managed by a report table.
>>>we have manny customers and app 400 reports no Problem
>>>
>>>dirk